So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?
Have they asked for superuser?
Via EVO on 4G with XDA App
awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device
krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su
Please delete
krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.
rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?
richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.
I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?
Related
hey well i got to this point :
# # /data/local/tmp/root
Click to expand...
Click to collapse
anyhow when i run this it says:
cp: can't stat '/sdcard/superuser.apk': no such file or directory
then is the same but with su
Click to expand...
Click to collapse
i went ahead and put sync anyhow and when i restart and run 'su' but is says: unknown user root
any ideas what i did wrong? :/
oh and btw somehow i have S-off...
i followed each step, but i just notices this... for some reason it wont let me push superuser.apk or su, all of the other files can be pushed... any ideas?
no one?
http://www.youtube.com/watch?v=tU9zn_BEth4 i did that way and it works for me.
but i have s-off i supposed to be rooted already but i do not have super user powers... what do i do
Did you copy the Superuser.apk file to the root of your SDcard?
yes i did, and su too and now when i put su on my phone it says unknown user root :/
i can get temporal rooting tough.
Use visionary r13 ... had same issue... worked for me
Get it from pauls visionary thread on Modaco.
Sent from my HTC Vision using XDA App
i had the same situation with u few days ago. just follow http://forum.xda-developers.com/showthread.php?t=834228 and u only need do the temp root part.
Delete visionary and superuser first, install terminal emulator from market.
on you pc:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Then on you G2, open a terminal emulator
Launch Terminal Emulator---/data/local/tmp/rage----Wait for the message: "Forked #### childs."------Menu > Reset Term - Terminal Emulator will exit.-----Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell----- run the /data/local/tmp/root script here.---sync.
In the last step, u can find the origin thread dose not let u do this. but, if you've got s-off, trust me, just do the last step "/data/local/tmp/root", and when u see a feedback "****files exist",then "sync",
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
u can also do what i suggested in the 8th floor.
o>c said:
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
Click to expand...
Click to collapse
r u rspt in Gfan? since u can read chinese, just look at here. http://www.hiapk.com/thread-631413-1-3.html
I made this thread to help solve such problem.
After I got S-off, I didn't have root either. I just jumped on visionary (made sure run on boot wasn't checked), clicked root now. And boom, that was it. Then I deleted visionary and I've had root ever since...
Does GingerBreak work with this version of Gingerbread 4.5.601.A955.Verizon.en.us? My phone is currently rooted with Z4Root 1.3. Is there an easy way of doing this?
Sam
Use the d3 root method. Works fine.
CM7GB-601
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I have the phone in PC Mode (instead of Mass Storage.) I don't know if that makes a difference.
The D3 Method worked great for me and my wife's phone.
Hi everyone,
I have the same question as CSSZiegler, but want to expand on it a little bit...
I have a Droid 2 that was rooted with Z4Root 1.3 several months ago. I also have SetCPU, SuperUser and Titanium Backup. No custom ROMs installed. Big Red just pushed down GB, and of course, I've lost root access. I'd like to regain root again without losing any contacts, Handcent messages, etc. I've read on several forums that the D2 can be rooted just like the D3 with a simple "one-click" operation referenced by quarky42 earlier.
Any opinions or experience with this? I greatly appreciate any and all assistance!
update
My phone downloads the update, I click install now... it reboots and starts the install, then about 35% of the way through, it turns to a triangle with ! Inside. Phone reboots and displays message software update failed. Anyone know where to find a logfile or have any suggestions?
Droid2 android 2.2.. rooted. No custom rom.
Did you fully SBF to stock using RSDLite?
Also http://forum.xda-developers.com/showthread.php?t=1246673 has a flashable version.
I will as soon as I get a computer again, thanks for the link. Unfortunately my mobo died yesterday. So I was hoping for an alternative solution. It would also be nice to keep all my texts.. I'll google that one.
So any ideas on the logs or an alternative solution?
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Ardalee said:
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Click to expand...
Click to collapse
I answered the thread you started with the process to un root and put your phone back to stock.
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
Awesome! That did the trick, thanks for the info
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
I would SBF back to Froyo with RSDLite and install the OTA GB from phone info updates. After that use the D3 one click root method and you're golden.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
acavallini said:
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
Click to expand...
Click to collapse
I searched the phone's sd card.. I couldn't find it... do you know where adb.exe is located?
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
idefiler6 said:
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
Click to expand...
Click to collapse
Finally got it to work... now.. I used motorola one click root.exe where you use the exe on the computer. Just out of curiosity, is there a one click method to unroot? Thanks!
Hi all,
I got my KF few days back, Rooted it, before I could install the android market, got forced update to 6.2.1. 2 days ago saw this new root method using BurritoRoot. Tried rooting it, seems successful, however, now when I arrived at the home page, I cant even open the Superuser app at all. It goes the same for the Root Explorer - prompting:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on. Click ok and restart the app and try again. Make sure u respond correctly to the Superuser prompt." Then it comes with a force close.
Seriously I do not know whats wrong with it, now i cant even use the root explorer for me to install Android Market.
Anybody can help me with it?
Million Thanks.
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
b63 said:
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
Click to expand...
Click to collapse
Im using the ROOT INSTALL - Method 1 and I downloaded the file from Rootzwiki, apparently the file is named "com.noshufou.android.su-1.apk". and I used the following commands:
adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
So which means I should use the Superuser -2.apk instead?
What should I do now? Download the Superuser-2 file and repeat the whole process again???
thanks.
yes - the new version seems to be the only one working with burritoroot
consider to use KFU to make things easier:
http://forum.xda-developers.com/showthread.php?t=1399889
should be option 2 (permanent root with superuser)
Built a version of Superuser.apk from the github source to make preferences work. All I've done is remove the code that checks for a new version. It works perfectly now.
http://dl.dropbox.com/u/19946299/Superuser.apk
Directions:
1. Uninstall your current version of Superuser with:
adb remount /system
adb shell rm -f /system/app/Superuser.apk
2. Install new one using adb
adb install Superuser.apk
Or
adb push Superuser.apk /system/app/Superuser.apk
Alternatively you can remove your current Superuser.apk with a root system file manager and install the new one the same way.
I've also put in the issue with ChainsDD on his issues list and where I found it, seems to be to do with the waiting thread when it requests the current su binary version.
Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?
I don't think it's busybox and the exact point that Superusers waits for the su binary to return the version number. The actual command works 100% OK, you can do the exact same commands in shell and it's fine. It seems to be something to do with the actual java exec thread. TB has the same issue, where as other backup apps (ultimate backup) do not, and they still call su binary. I'm still trying to figure it out.
GavChap said:
adb shell rm -f /system/Superuser.apk
Click to expand...
Click to collapse
change to:
Code:
adb shell rm -f /system[COLOR="Red"]/app[/COLOR]/Superuser.apk
thanks
edit: and i had to push the su app instead of install
Good job...works nice. Did you commit ur change to source so future builds will be free from this bug? If not, commit to either evervolv or cm...or detail the change in source and I can.
Thanks
Sent from classicnerd ICS Touchpad
Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.
Working now. Reset it and installed good to go
Redflea said:
Thanks....this did not fix the crash/Reddit issue with TiBU current version...installed and launched TiBU, and it froze and then rebooted my TO, tried it two times.
Click to expand...
Click to collapse
This is a workaround rather than a fix. The su binary is fine. There is a kernel issue that causes the crash. The logs I have state it's with the msm ioctl code.
There are other root using apps that don't crash at all.
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
TMan459 said:
Thanks for the post. I'm wondering, and yes I've searched plenty on XDA and RootzWiki, will this fix su issues all around? For example, using TB 4.0.2 sends my CM9 TP into a reboot. I've read this may be an issue with Busybox.
Any insight anyone?
Click to expand...
Click to collapse
This doesn't fix the SU problems, just the Superuser front end.
Thanks for the tips.
I replaced my Superuser.apk with yours and now I can get into the settings without FC.
I used root explorer to replace the files but I also had to changed the permissions of your version of the superuser.apk to match the other files (rw-r--r--) to work properly.
One thing I noticed that even though I can get in to settings in SU, I still cannot update the binaries. If scans for updates but when I ask it to actually update the binary, it reboots the TP.
Thanks anyways...
There is a bugfix kernel coming from the CM team soon that'll fix these issues, I've tested the fix on my kernel and it's working fine.
So I just updated my kernel (bricked-kernel 2.6.35) to fix the TIBU issues and as a side benefit, my SU no longer reboots the TP when I try to update the binaries. It finds the update and tries to apply the update. It returns an "update failed" message, but it no longer hard reboots my TP.
I think it's getting closer to being perfect... ^_^
You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot
GavChap said:
You can try my kernel if you like
http://dl.dropbox.com/u/19946299/uImage.CyanogenMod
download onto your computer, boot into ClockworkMod
Then do the following using adb on the computer
adb mount /boot
(optional) adb shell mv /boot/uImage.CyanogenMod /boot/uImage.CyanogenMod.old
adb push uImage.CyanogenMod /boot/uImage.CyanogenMod
adb umount /boot
adb reboot
Click to expand...
Click to collapse
Is this based off just the CM team or do you also use the commit's from Bricked-Kernel?
I had to re-copy the superuser.apk after the alpha 0.5 update. I will say with the 0.5 update and this adjustment, all is well. Couldn't be happier.
Best thing to do about Superuser if you get force close on setting in CM9A0.5 is to remove the Superuser app using Titanium Backup or root explorer. Then install the one from the Android Market, settings works 100% now. I think the one in CM90.5 is an older version.
Good tip! Worked for me on .5 and can now use TB from market. Thanks.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.