Hi
i rooted my Phone (Gingerbread XWJVI) a few Days ago with CF-Root 3.7.
Everything went fine, thanks to the great work from Chainfire
Unfortunatly i tried to install a newer Busybox Version.
I tried Busybox Installer (JRummy) from Market, unfortunatly the Connection got lost during download/install.
After that i tried installing Busybox (Stericson) which gave me an Error :
Failure /system/xbin/ could not be remounted as RW!
Root Checker gives:
Code:
Congratulations ...
Superuser.apk - com. ... is installed.
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:
Segmentation fault
Standard su binary location : ls -l /system/xbin/su:
Segmentation fault
Alternate su binary location :
Segmentation fault
and for Busybox verification:
Code:
Installed Busybox Version:
Busybox is not sharing its version information.
Busybox supports the folloeing applets:
Busybox is not sharing its supported applets.
So i messed things up.
Is there any way of getting Busybox 1.16androidminimal back which came with CF-Root 3.7 ?
Any help apreciated.
Try flashing CF-Root 3.7 again via odin
[put ur sgs into download mode {HOME+VOL DOWN+POWER}, load kernel in pda {DO NOT select REPARTITION} and flash] instructions are here
Or else you can flash a new rooted/custom rom via odin.
Copy/Back up all your personal data to ur pc/sd before flashing. because it will wipe!!!
Reflashed CF-Root and wiped.
No Result, Busybox stayed messed up.
The problem may be a differnet one.
If i just want to get a directory listing in terminal,
ls gives me a segmentation fault.
If i do a "toolbox ls" everything is fine.
Related
Hi there!
I hope, this is the correct subforum......
Have anyone installed OpenVPN on the Galaxy S Plus I9001 any have a
good discription for me to do this?
Hope, you can help me!
Thanks for this, maze-m
Q&A section is here, please don't post questions here in development section or they will either not be answered or deleted...
Here's how I did it:
1. Root your phone using KeksFlip's excellent supereasy guide
2. Install Busybox. I used BusyBox Installer by JRummy16 from the Market and installed the latest version in /system/xbin.
3. Install OpenVPN Installer and and OpenVPN Settings from the Market.
4. Run OpenVPN Installer and install into /system/xbin. When it asks you for the location of BusyBox, say /system/xbin/bb
5. Create symlinks of ipconfig and route inside /system/xbin/bb:
a) Enable USB debugging mode (Settings -> Applications -> Development) and connect your phone to your PC via USB. You will need the adb.exe commandline tool form KeksFlip's rooting guide.
b)
Code:
adb remount
adb shell
$ su
# mkdir /system/xbin/bb
# ln -s /system/xbin/ipconfig /system/xbin/bb/ipconfig
# ln -s /system/xbin/route /system/xbin/bb/route
6. Upload your OpenVPN configuration files and keys to your phone and put them in /sdcard/openvpn
7. You will need a TUN kernel driver module. I have attached the one I made for my kernel to this post. If your kernel version is 2.6.35.7-perf, you can use it otherwise you will need a different one. Put the tun.ko file in /sdcard/openvpn.
8. Run OpenVPN Settings and under Menu -> Advanced configure the following:
Code:
- Load tun kernel module ✓
- TUN module settings
- Load module using: insmod
- Path to tun module: /sdcard/openvpn/tun.ko
9. Start your VPN connection
Good luck!
dbx4 said:
Here's how I did it:
1. Root your phone using KeksFlip's excellent supereasy guide
2. Install Busybox. I used BusyBox Installer by JRummy16 from the Market and installed the latest version in /system/xbin.
3. Install OpenVPN Installer and and OpenVPN Settings from the Market.
.........
Good luck!
Click to expand...
Click to collapse
I have samsung Galaxy S Plus phone (firmware I9001XXKPF), I want to build a module tun.
tell me plz the link where to download the source code for kernel 2.6.35.7-perf (androind 2.3.5) to compile the module yourself.
Hi, I rooted my Galaxy S Plus using KeksFlip's guide. I then tried to install OpenVPN dbx4's method. However I got stuck at adb remount:
Code:
D:\temp\adb>adb remount
remount failed: Operation not permitted
D:\temp\adb>adb shell
$ su
su
# mkdir /system/xbin/bb
mkdir /system/xbin/bb
mkdir failed for /system/xbin/bb, Read-only file system
#
Is there anything I'm doing wrong?
Thanks!
You have to remount the system-filesystem on GT-i9001 yourself in adb shell:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p15 /system
When you're done, mount read only again:
mount -o ro,remount -t ext4 /dev/block/mmcblk0p15 /system
Can anyone tell me why the module fails to insert even though it's the same kernel number?
"init_module tun.ko failed (exec format error).
I have the same problem with cifs.ko that is also built for my phone's kernel.
Hey all, I rooted my phone using SuperOneClick, Was fine, restarted my phone all good. Then I decided to install a custom rom, That also worked all fine except now that I've installed it, my phone seems to not be rooted (I checked using root checker before installing rom and after, said it was rooted before, But now it says it's not rooted) What could be causing this? I've repaired it and started over 3 times with the same result. Could someone please shed some light? Thank you.
Try with other custom rom....maybe rom that you installed causing it
Sent from my Shakira using XDA App
Some roms like, per exemple, HAKA's Original W8 Room aren't rooted!
Try another rom or, try rooting that rom
Oh ok, thanks for the reply, tried rerooting, it ended up going to not responding, I have access to system files, the su file is there, but I don't know about the other files that allow the device to be rooted. Is there some way I can copy and paste the rest of the su binary's? The ROM came with super user app so I just assumed it was rooted.
Sent from my X8 using XDA App
Which Tom, clone tell us a little bit more
Sent from my Xperia X8 using XDA App
Running; cm7-138 (2.3.4)
Found it here; "
Code:
http://forum.xda-developers.com/showthread.php?t=914513"
Info from Root Checker;
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System environment PATH: /sbin/vendor/bin/system/sbin/system/bin/system/xbin
The adb binary is set to default shell user access is root
Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx 1 0 0 15 oct 19
22:21 /system/bin/su -> /system/xbin/su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-xr-x 1 0 0 26332 aug 1
2008/system/xbin/su
Alternate su binary location
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
I'm not sure if that was any help, put it there just incase.
Hope that's enough info, If you need more just ask
Hi I'm using CM7.1 and it works well, then I noticed most apps that need root access stopped working.
root explorer won't even launch, rom manager can't run any command, but terminal and SSH tunnel works fine.
So I installed root checker, witch says 'you have root access' but check results are 'permission denied'
Here is the result:
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your Optimus 2X device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Click to expand...
Click to collapse
BusyBox file was not found in the system declared path.
Simple method to install BusyBox is to search for the BusyBox app by Stericson in the market!
Results provided on your Optimus 2X device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Click to expand...
Click to collapse
Tried to install busybox with busybox installer v5.5, didn't work. (requires root access)
Downloaded latest superuser and binary, flashed via CWM didn't work.
Reset superuser and tried to update binary from superuser binary updater fail checking md5sum.
I also tried fix permission from CWM but didn't work neither.
Any help would be appriciated.
Thanks!
any suggestions?
try to reflash again, btw what is your CM 7.1 built nightly or stable? i just flash nightly 204 and it works fine here
antec123 said:
try to reflash again, btw what is your CM 7.1 built nightly or stable? i just flash nightly 204 and it works fine here
Click to expand...
Click to collapse
Thanks for the reply! I'll try that and post back.
It's CM7.1 stable version I'm using.
BTW do I need to wipe cache?
update: reflashing works
lqhan said:
Thanks for the reply! I'll try that and post back.
It's CM7.1 stable version I'm using.
BTW do I need to wipe cache?
update: reflashing works
Click to expand...
Click to collapse
glad that i can help. yes indeed you should cache wipe. i usually wipe the dalvik cache too
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
clyde1914 said:
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
Click to expand...
Click to collapse
Try rebooting.
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link Here. If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
nobe1976 said:
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
Click to expand...
Click to collapse
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
clyde1914 said:
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
Click to expand...
Click to collapse
I would stick with the HOB just to keep the data. The only route I have found that will successfully re root it is done with Linux. It can be done running Linux on a thumb drive as long as there was space created for updates.
Sent from my XT875 using Xparent Red Tapatalk 2
If that doesn't work and you need restore it to JB, here are the relevant links:
FXZ files for Bionic:
http://forum.xda-developers.com/showthread.php?t=2240725
RSD Lite Example (not for bionic, but gets you some of the links you'll need):
http://forum.xda-developers.com/showthread.php?t=2231249
If you want to try it from linux, fastboot from linux:
http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz
And if you need to root once you flash your JB stock image, you'll need something like this:
Easy root:
http://forum.xda-developers.com/showthread.php?t=2256439
Samsung S3 i9305 supersu binary problem
Quote:
Originally Posted by cbmk
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix. Any help will be appreciated this is the first time I have rooted.
PS. If this post is in the wrong place please advise where itshould be.
Thanks
S