Related
I updated busybox in /system/xbin but still see the old busybox revision when I type busy box at the ADB shell prompt, I found:
/sbin # ls -l busybox
lrwxrwxrwx 1 root root 8 Aug 17 01:35 busybox -> recovery
looks to be a link to busybox in recovery, I cannot get to recovery..
Any ideas if that actually belongs there?
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
adrynalyne said:
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
Click to expand...
Click to collapse
Now that our NAND is (relatively) unprotected, can I use Stericson's busybox installer to place a copy that will be accessible anytime I use ash via adb or terminal, or do I (can I) simply push busybox to /system/bin to make it a native part of android's command path? OR, do I have to use ~/xbin like the OP? It seems until we got S-OFF, busybox commands rarely pointed back to busybox automatically, I always had to spell-out "busybox" as a prefix, unlike my G1, where all ROMs after a while had busybox installed natively, from /system/bin, I assume.
thanks for advice in advance
Yep, you can use his installer on the market just fine.
adrynalyne said:
Files from /sbin are not in the path for Android, just in recovery.
That particular recovery is a different version.
If you just type busybox from a terminal, it should give a correct version.
If not, check /system/xbin or /system/bin, because you have an old version somewhere...or never updated like you thought.
Click to expand...
Click to collapse
Thank you, everything is working busybox 1.15.3 is loaded, for an added measure I ran permissions.
Hello Friends,
I am using DHD since last few weeks, i have downgraded it to 1.32 and can use superuser access. But now i have been facing new problem. i am not able to reboot using terminal emulator. is there anything missing? I was adding new font to my system fonts, but at the end of it we requires to reboot it, its simply said "not permitted!"
can anyone please help me in this regards!
Thanks in advance.
Are you on a custom rom?
I had a quick look in leedroid with root explorer and it seems the permissions are incorrect for /system/bin/reboot.
rwsr-xr-x where it should be rwxr-xr-x
-----
Someone Swyped my idea.
Using Unity 1.29,have checked my permissions on /system/bin/ reboot -rwxr-xr-x root shell,busybox is also good tried
$ su
#reboot
and get "not permitted"
I know i could just use the buttons but would like to be able to do it from the terminal,checked on a nandroid backup of CM7.03 and the command works from terminal,anybody any ideas how to get it working? Its got me completely stumpted!!!!!!!!!!!!!
also happens to me with Revolution HD
Try from the terminal
$su
#reboot -f
BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
Try it and see how you go
I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?
ayang02 said:
I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?
Click to expand...
Click to collapse
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.
yakalid said:
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.
Click to expand...
Click to collapse
I've figured out the solution to my problem: just re-push su & Superuser.apk to /system/su and /system/apps/Superuser.apk respectively.
Basically I referenced this thread: http://forum.xda-developers.com/showthread.php?t=1531865
Since I already have su and Superuser.apk in my /system (although I think I tainted both files), all I needed to do was grab clean versions of su and Superuser.apk and adb push em through and type "adb shell su" to make the # appear. I was even able to update su binary within Superuser, awesome :good:
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
Click to expand...
Click to collapse
Hope this helps with people who are having troubles with Superuser/su not gaining root access.
If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.
Matridom said:
If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.
Click to expand...
Click to collapse
I guess it makes sense, the only real issue was my su permissions.
I did this with a locked bootloader btw.
Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help
kout said:
Hi, I've tried SuperSU and SuperUser.
apps and adb shell can't access the /data partition.
it says that I don't have enough permissions ...
with adb shell I can cd to it, but even an "ls" says operation not permitted
I can access it just fine in CWM using adb shell
all other root directory works fine....
Does anybody know what's going on ? did i miss something ? I'm no expert when it comes to this
thanks for your help
Click to expand...
Click to collapse
After typing adb shell and entering you have to type su and press enter again, then you`ll have the permissions you need
But how come root browser can't access that directory?
And why can I go to /system without having to type su first
kout said:
But how come root browser can't access that directory?
And why can I go to /system without having to type su first
Click to expand...
Click to collapse
How do you mean: root browser/ file manager on the phone to access system date? You have to be rooted to access system data on the phone. What exactly do you want to do?
Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S
kout said:
Weird stuff, it's working with solid explorer, I had tried with rom toolbox browser and some other root browser from the play store and it wouldn't work
Thanks for the "su" tip I forgot you had to be su to access that folder :-S
Click to expand...
Click to collapse
Is you`re phone rooted mate? The su command is for adb from your computer!
Of course it's rooted, I do have a bit of experience with that. It's just weird that certain root browser can't access the data partition despite having granted su permission to the app. Anyway its working great with solid explorer now, and with adb I've got the su command
I actually have the voice stuck on the same street in navigation, (known bug) so I had to delete some cached speech data in the data partition
I did it through cwm but I was wondering why it wasn't letting me do it once booted. Anyway thanks
After dabbling around in some murky waters trying to achieve root, and going trough some 2010 stuff I did, I did discover a method I devised back then works to some extent, strangely.
Using fastboot (boot) to a TWRP recovery image (TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img), mounting /system, and pushing a version of busybox, bash and using the supersu su binary already in the TWRP recovery image.
boot-new.img.bz2.zip (rename to boot-new.img.bz2 before extracting -.Just TWRP_v2.8.6.0_honami, with a different kernel and dt image included to boot from fastboot)
bash and busybox i compiled from git and debian sources yesterday/today
Basically this; (use only for reference.)
Code:
# Magically push all files in place here.
# Optionally, move /system/bin/sh out of the way and link /system/bin/sh to bash
./"$ADB" shell "chmod 755 /system/bin/bash && chown 0.0 /system/bin/bash"
./"$ADB" shell "chmod 4755 /system/bin/busybox && chown 0.0 /system/bin/busybox"
# TWRP
#./"$ADB" shell "cp /supersu/su /system/bin/_su"
./"$ADB" shell "cp /supersu/su /system/bin/su"
./"$ADB" shell "cp /supersu/supolicy /supersu/su /system/xbin"
./"$ADB" shell "cp /supersu/libsupol.so /system/lib/"
./"$ADB" shell "chmod 0644 /system/lib/libsupol.so && chown 0.0 /system/lib/libsupol.so"
./"$ADB" shell "cp -r /supersu /system/app/SuperSU"
./"$ADB" shell "chmod 0755 /system/app/SuperSU && chown 0.0 /system/app/SuperSU && chmod 0644 /system/app/SuperSU/SuperSU.apk"
#
#./"$ADB" shell "chmod 4755 /system/bin/_su && chown 0.0 /system/bin/_su"
#./"$ADB" shell "echo "busybox su -c "_su"" > /system/bin/su" # or busybox su -c "_su -c /system/bin/sh-org"
./"$ADB" shell "chmod 4755 /system/bin/su /system/xbin/su* && chown 0.0 /system/bin/su system/xbin/su*"
# Quite dangerous - Suggest moving passwd when in normal use
./"$ADB" shell "echo "root::0:0:0:/root:/system/bin/sh" > /system/etc/passwd"
./"$ADB" shell "chmod 0644 /system/etc/passwd"
Next step, to remount /system with write permissions from a normal boot, I think, would be to modify boot.img/default.prop and set "ro.secure=0"
Thought I had done this prior, I run with touch disabled as I cracked my screen (impressively massive drop of at least 30 cm! - onto object.. ) ... I could not remount system when I first tried.
Notes:
If i adb in early i can use supersu/su to gain root, when system is loaded busybox su -c ""supersu/"su" works. - NO AUTH
Hm, updated SuperSU via google play and suddenly it realized it was rooted . = ) Still keeping the supersu/su intact in /system/*bin
Thankfully I've been unsuccessful in grabbing root from /data/local/tmp this way as of now. Seems the permissions are reset. Though getting root without any auth is a serious matter no matter how you flip the coin. At least it's not as easy as pushing an archive to /data/local/tmp and running busybox su -c su. Also with a modified busybox you could easily skip the part where I write a /etc/passwd with no password.. Incredibly handy if you need root without Android running, say with setprop ctl.stop zygote, media and bootanim. But incredibly dangerous!
Fastboot to attached TWRP and install [STABLE][2016.02.02] SuperSU v2.65 - http://forum.xda-developers.com/showthread.php?t=1538053 - drop the zip to somewhere on the device and use the install function, i installed supersu via google play first. Attached is the kernel image i'm using. On a side-note, the script above failed .
Apart from this, the attached gnu-tools i will have to update... Got a neon flags optimized for out cpu and all, but that's for a different day.
Cheers, have a good one mates
Noob question: what is the difference between using this method for root and kingroot method? Which is better to use?
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
threader said:
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
Click to expand...
Click to collapse
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Noticed my boot img was rebooting sometimes, went off and updated my compiler toolchain and had a look at the kernel and recent developments.
Had a look at X-Honami v6 and ported some parts of that effort to the latter Sony kernel used in 14.6.a.1.216.
* Messed around with memutils and implemented ARM_PLD_64BYTE and USE_LDRDSTRD_OVER_LDMSTM atop memutils from the Xperia-dev unified kernel. - this needs some testing but appears to be stable at least with the options turned on.
* Slight overclock of GPU to 533 mhz, and underclock to 27 mhz on idle.
* Has kexec hardboot
I cannot busybox su -c su with this kernel. Which is only useful for developers anyway. You'd be wise in running some benchmarks before and after the flash.
Kernel needs to be flashed via fastboot.
Source:
https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/
DectonX said:
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Click to expand...
Click to collapse
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
Ok i have done step #1 by manually updating supersu and it deleted the kingroot by itself. Now i need answer for #2 only, Which recovery should i install in stock based rom ?
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
DectonX said:
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
Click to expand...
Click to collapse
Thanks a lot..
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
VikasG09 said:
Thanks a lot..
Click to expand...
Click to collapse
threader said:
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
Click to expand...
Click to collapse
I just used kingroot, unlocked bootloader, flashed dual recovery, flashed prerooted Rom. That's it. Easy as pie.
Sent from my D5503 using Tapatalk