Related
I've noticed that the su binary installed by superuser doesn't survive a reboot. Anyone else have this problem? Any fixes?
Sent from my SPH-D700 using XDA App
Same here. Have to re update after each reboot
Sent from my SPH-D700 using Tapatalk
same here, had to update the binary too
How do you update the su?
Launch superuser, go to settings and scroll to the bottom.
Sent from my SPH-D700 using XDA App
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
dangdang said:
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
How did you update it yourself?
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Code:
#cp /sdx/su /system/bin/jk-su
cp: not found
the last part does not work (i have the same root method)
i have to re-root the phone when i get home today. but i will try to move the updated binary with root explorer instead of the command line.
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
dangdang said:
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
Click to expand...
Click to collapse
will try I had the same issues
dangdang said:
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have this exact same problem on my Samsung Moment (have to update SU every reboot).
The directory structure seem a bit different. For example, there's no /system/bin/jk-su (in fact, if I find / -name 'jk-su' I get no results at all).
I am poking around the directory structure trying to figure out where to find the source and destination su files that I'm going to have to overwrite and I can't seem to figure which is which. Does anyone have any idea how to do the functional equivalent of dangdang's post on a Moment?
Thanks!
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
I was about to say. WTF is everyone talking about SU not surviving a reboot /noodlescratcher
davidrules7778 said:
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
Click to expand...
Click to collapse
k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
lol. i hear ya!
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
most likely SU is built into your kernel and short of rebuilding or repacking your kernel you cant update it..
I have a samsung galaxy s I9000 running Gingerbread will this work for me..?
I apologize if this is already answered somewhere. I searched everywhere and could not find anything, but I might be using the wrong wording.
Anyways I am attempting to root my G2. I have managed to get adb onto the computer and it recognizes my phone. However, the next step in the wiki says to:
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ 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/*
However, it gives me error messages such as 'adb' is not recognized. I'm sure I am missing stupid but I cannot figure it out. Thanks in advance.
Just use visionary, it is much easier. Click temp root and when it is done perm root
http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
Sent from my HTC Desire using XDA Premium App
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
o0olove said:
I don't trust visionary. I want to go about this the safest way which is the gfree method.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used visionary and it worked just fine, but you do what you feel best with
Sent from my HTC Desire using XDA Premium App
bradley_e_smith said:
Make sure that the adb (and other stuff tha got installed) is in your PATH environment, or cd to that diectory and work from there.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I checked the path a few times because I thought that was the problem. However, it all looks good. I'm going to try on another computer tonight and see if that helps.
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
I used visionary and terminal emulator and haven't had any problems at all.
_________________________________
Sent from my CM7 T-Mobile G2 using XDA app
tazz9690 said:
Did you make sure that all the necessary drivers were installed?
When you type 'ADB Devices' does it show your phone?
Click to expand...
Click to collapse
Yes it shows my phone when I type 'ADB Devices' That's what's causing my confusion. I've reinstalled all the drivers that are needed. From what I am seeing it SHOULD work.
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
You need to set permision /rw ,to system folder via root explore,then do adb push
bittu4u4ever said:
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
Click to expand...
Click to collapse
Sent from my Wildfire using XDA App
luxandroid said:
You need to set permision /rw ,to system folder via root explore,then do adb push
Sent from my Wildfire using XDA App
Click to expand...
Click to collapse
(OfCourse throughout the process /system is mounted as re-write)
Click to expand...
Click to collapse
As mentioned in my question i hav permission of rw(read-write) already throught the process..
I am using hell fire,pushed or pulled files but not as root user,just went to my tools folder where adb is and did adb push,try like that...
Sent from my Wildfire using XDA App
Have you already tried "adb remount"?
cobje said:
Have you already tried "adb remount"?
Click to expand...
Click to collapse
This should indeed solve all your problems. Just type that command, wait for the "remount succeeded" notification and than try to write in your system folders.
The reason is that your /system is not mounted as read/write (r/w) when you boot your phone, but as read-only (r/o). So afther the remount command /systemfiles will stay r/w, but when you reboot your phone, it will return r/o again.
Erwin
Im using linux and im trying to install Galaxy S II theme that posted at themes and apps forum
that what im doing
[email protected]:~$ adb devices
List of devices attached
43423541314434573458 device
[email protected]:~$ cd /home/aviv/GTHEME
[email protected]:~/GTHEME$ adb push android.policy.jar /sdcard/
failed to copy 'android.policy.jar' to '/sdcard//android.policy.jar': Permission denied
Click to expand...
Click to collapse
need help :|
Locked Bootloader with root
adb on linux - ubuntu 11.04
LightingZ said:
Im using linux and im trying to install Galaxy S II theme that posted at themes and apps forum
that what im doing
need help :|
Locked Bootloader with root
adb on linux - ubuntu 11.04
Click to expand...
Click to collapse
What Rom / kernel are you running?
Sent from my R800x using xda premium
Orginal kernel and SE World Generic 2.3.3
adb typically needs to be run as root.
zerojay said:
adb typically needs to be run as root.
Click to expand...
Click to collapse
How do i run it with root?
if i write sudo adb <command> (example)
it's says sudo: adb no such command
Run the command su first, it'll ask you for your root password (if you set it up) and root persists until you exit
Sent from my R800x using XDA App
su + adb command (su adb push)
not works :|
ok
i got SUPERUSER PERMISSION
i type
adb shell
then
su
and then it asked for allow or deny i press allow
no effects yet
Just double checking, are you running as root on ubuntu?
Sent from my R800x using XDA App
just type su on it's own and hit enter, then adb commands on a separate line (after entering linux root password, obviously)
also (i'm not sure how much this will affect it) try running chmod on adb...
Happened to me, make sure your SD card isn't mounted while your using adb
Sent from my R800i using XDA App
Whenever I try and mount system as writable I get
Mount: operation not permitted
The error occurs whether I use adb or terminal.
Sorry! Realized after posting I'd gone into the wrong forum! Could a mod move it please? Or delete it and I'll make a new one?
Maybe try to download the ICS rooting.zip and run the macro using fastboot.
Open up terminal emulator and type:
su
mount -o remount,rw / system
Sent from my SPH-D710 using xda premium
bmxrideher said:
Open up terminal emulator and type:
su
mount -o remount,rw / system
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This won't work on the a100. You still need the mempodroid exploit.
Works on mine. It's only a small price to pay to have the CM9 goodness on my tablet and it's R/W until next reboot.
Sent from my SPH-D710 using xda premium
bmxrideher said:
Works on mine. It's only a small price to pay to have the CM9 goodness on my tablet and it's R/W until next reboot.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?
bellaale said:
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?
Click to expand...
Click to collapse
Either of the ICS root methods in the dev section should fix it
bellaale said:
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?
Click to expand...
Click to collapse
You might try "busybox" after the su and before the mount command, e.g.: 'busybox mount -o remount,rw /system'
Busybox knows about these things.
AZBOLIVE
just type in "su" enter it then type commands as normal.
your permissions wont let you at present,
letting the system know to run su works good.
hope it helps!