Hello,
I'm trying to reinstall BusyBox on a Stock rom in a GT-S5830C but I get this error when using BusyBox Installer for any version of BusyBox:
reloc_library[1312]: 7993 cannot locate 'android_reboot'...
CANNOT LINK EXECUTABLE
Click to expand...
Click to collapse
I've already installed BusyBox once using another BusyBox app, but that app is very slow and it seems it is not working properly (BusyBox by Stephen). I'm trying to apply the modifications that enable init.d in a Stock rom (http://forum.xda-developers.com/showthread.php?t=1422061&page=2), and BusyBox is a important part of it, it looks like no busybox command is working.
Sorry for bad english,
Thanks for reading!
It looks like I fixed, removed BusyBox Installer by Stephen, unrooted and rooted phone again (recovery mode), cleaned cache partition (recovery mode), fixed permissions (CWM recovery), installed BusyBox Installer by Stephen again, installed BusyBox with success.
I have the same problem
eumax said:
It looks like I fixed, removed BusyBox Installer by Stephen, unrooted and rooted phone again (recovery mode), cleaned cache partition (recovery mode), fixed permissions (CWM recovery), installed BusyBox Installer by Stephen again, installed BusyBox with success.
Click to expand...
Click to collapse
I have the same problem code 1312, 2739. I currently have busybox installed in system/xbin. But I allowed a smart install. After experiencing the downloading of the new busybox installer. Tried to update busybox. It said it is not compatible with my version 1.20.2 ? Relly don't want to go the unroot and root course. Maybe a simpler way. Sorry if I put this request in the wrong place. Thanks
wally18324 said:
I have the same problem code 1312, 2739. I currently have busybox installed in system/xbin. But I allowed a smart install. After experiencing the downloading of the new busybox installer. Tried to update busybox. It said it is not compatible with my version 1.20.2 ? Relly don't want to go the unroot and root course. Maybe a simpler way. Sorry if I put this request in the wrong place. Thanks
Click to expand...
Click to collapse
Put the busybox binary in either system/bin or system/xbin using root explorer. Set correct permissions. Then uninstall busybox installer.
Reboot into cwm and do a fix permissions. This should help, but if it doesn't, you can always go the unroot thing..
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Related
Hi,
I cannot get root access on my terminal. The following is my configuration:
Froyo 2.2
PC: GT-I9000HKYTIM
PDA: GT-I9000AIJP6
PHONE: GT-I9000XXJPP
CSC: GT-I9000TIMJP4
Recovery : 3e
I installed speedmod k13e, but i cannot enable tweaks, bln and root.
Whenever i enter recovery mod i try to install root (simple) from the speedmod/ulk menu, at the end of the process it says "Done!" but when i reboot titanium backup complains that i do not have root privilegies.
Furthermore when i try to enable tweaks, every tweak i choose prompts "disabled". The same thing happend when i try to turn on BLN.
Any idea?
Thank you for you help.
Mattia.
Check if you actually have the Super User app on your phone.
If you don't have it download busybox from TitaniumBackup.
The Froyo Speedmod is ultrastable so this is quite odd to me.
If neither of this works I think you might have to reflash the kernel.
Hi,
thank you for your reply.
I did not have the superuser app installed and i did not find a way to download busybox from TitaniumBackup.
So i installed both superuser and busybox from the market.
I run superuser, then TitaniumBackup, but it does not start and it does not ask for root privileges.
In the same way i run superuser, then the BusyBox installer, but it does not start and it does not ask for root privileges.
I reflashed SpeedMod, but nothing has changed.
I forgot to say taht my sgs is branded and i did not unbrand it. Other things i should try?
Mattia.
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
aittam said:
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
Click to expand...
Click to collapse
yea I guess your /system probably is full. to change that delete for example google maps (you can just download and install it from the market) from /system/app with root explorer or go into recovery and convert the filesystem the conversion will give you some more free space even if you change back to rfs afterwards
I did it using ADB Shell.
From the shell both su and busybox worked like a charm.
So eventually i managed to do my backups!
Mattia.
GT-P3110 by RomsWell
Base.P3110OXXBLH1 For the GT-P3110
This is a mostly stock version of the OTA. With a some of the more basic features added.
De-Odex
Zip Align
Rooted
init.d Support
I do not own this device.
Install Instructions
Flash thru Custom Recovery
DO NOT UPDATE SUPERUSER BINARYS YOU WILL LOSE ROOT!
If coming from CM you will need to do a full wipe including System before flashing.
Download Here
Thanks for the ROM. I just wanted to mention that the "su" binary included in this ROM does not match the "su" binary for Superuser 3.1.3. You have the "su" binary for Superuser 3.0.7 and the Superuser.apk 3.1.3. Just need to update the "su" binary to match the 3.1.3 version.
Regards.
Tsjoklat said:
Thanks for the ROM. I just wanted to mention that the "su" binary included in this ROM does not match the "su" binary for Superuser 3.1.3. You have the "su" binary for Superuser 3.0.7 and the Superuser.apk 3.1.3. Just need to update the "su" binary to match the 3.1.3 version.
Regards.
Click to expand...
Click to collapse
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
deleted
? This is for the 3110. The 3113 has a New update or so samfirm says. But I just got home from work. I prolly won't post it till morning.
RomsWell said:
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
Click to expand...
Click to collapse
It should work. I have fixed it for my rom and its fine.
Any chances of this working on 5113 or where I can find a similar stock "tweaked" ROM?
Thanks!
RomsWell said:
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
Click to expand...
Click to collapse
Sorry for doubting you. I tried it with the new binary and it indeed does not work. But the 3.0.7 version works. I wonder why? When I rooted the stock rom (odexed), then the new binary (3.1.3) worked.
I'm not sure but its driving me nuts. I spent a week thinking I was doing something wrong. I have the latest superSU working and updatable. I'm working on the newest p3113 ota if it works on that. I'll fix it on the current uploads.
I have switched over to SuperSU 0.95 and it is working fine. Although, I am noticing some strange behaviour with TiBackup. When I try to "clean dalvik cache", TiBackup just freezes up every time. I'm starting to think that these problems have to do with the "De-Odex" procedure. Would it be possible to create an untouched stock rom (odexed) that is CWM flashable?
Best Regards.
Note:
When I extracted the samsung package (P3110OXXBLH1) to create a custom ROM for testing, I noticed that "boot.img" is not the same as the one in your ROM.
When I extract boot.img from P3110OXXBLH1, this is what I get:
4540672 2012-08-07 02:31 boot.img
MD5SUM:
a08c7f58d6aa99a648e55859281375fe boot.img
Is there something you do to the boot.img to change the size?
Edit: I got it working now The problem was that I was still missing a few files from /system/bin. But, the kernel in your ROM is not the stock kernel for this ROM.
Edit2: The latest su binary for Superuser (3.1.3) is still not working. This leads me to believe that the problem is NOT with the de-odex process. The last stock ROM that I tested with su (3.1.3) was Android 4.0.3. So, maybe the latest Superuser su binary just doesnt work with this version.
Edit3: I found some problems with the updater-script. /system/bin/sh is being linked twice, to two different apps. Also, there is a recursive chmod in the wrong location that is overwriting the chmod permissions in /system/xbin.
symlink("mksh", "/system/bin/sh");
symlink("/system/bin/bash", "/system/bin/sh");
I think the "bash" one needs to be removed.
Edit4: Changing the shell did not fix anything with Superuser.
Hi,
I'm rooted with the stock ROM but having some trouble installing busybox using the installer from the play store.
Using the 'normal' installation method it tells me if failed for an unknown reason or reboots the phone.
Any ideas?
Download root checker and verify that you have root
If you do, try another app, if not, you can always download the busybox binary yourself and install it :good:
Root verified, other root apps work fine also. Will try another busy box method
None of the installers seem to work, should I be pushing to /system/bin correct?
are you on the 1.27 stock rom? zhis rom is odexed and i got the same problem. after installing a deodexed rom with 1.28 i was able to install it
Stock 1.28 - Odexed
i think the odexed is the problem
Yeah, push to /system/bin
Then run (in a terminal / shell)
Code:
busybox install ./
CNexus said:
Yeah, push to /system/bin
Then run (in a terminal / shell)
Code:
busybox install ./
Click to expand...
Click to collapse
or install in recovery... that works for me!
snoozor said:
or install in recovery... that works for me!
Click to expand...
Click to collapse
Might be a dumb ass question here but I can't find flashable zip file to install Busybox through recovery, anyone got a link or tell me where I can find one?
Thanks.
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
One Hype said:
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
Click to expand...
Click to collapse
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
KiraYahiroz said:
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
One Hype said:
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
Click to expand...
Click to collapse
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
KiraYahiroz said:
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
Click to expand...
Click to collapse
Just did this buy with v.1.8 of SuperSU and everything worked perfect. Thank you
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob