Related
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.
____________________________________
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.
[Q] can anyone share me how to change amend script & binary on cwm and edify script & binary on xrecovery :beer:
unsigned
search it of course you will get it
agungtem said:
[Q] can anyone share me how to change amend script & binary on cwm and edify script & binary on xrecovery :beer:
unsigned
Click to expand...
Click to collapse
why would you want to change it? you soft mod rom?
I followed a guide to create a flashable zip from FTF i created the zip but when i try to flash it CWM says installation aborted without any errors
i searched the internet i found that the update binary and updater script doesn't support my device . that why i need the update binary and the updater script
username249 said:
I followed a guide to create a flashable zip from FTF i created the zip but when i try to flash it CWM says installation aborted without any errors
i searched the internet i found that the update binary and updater script doesn't support my device . that why i need the update binary and the updater script
Click to expand...
Click to collapse
you want to flash a full rom ?
Ben Ling said:
you want to flash a full rom ?
Click to expand...
Click to collapse
Stock rom
So I'm using Chainfires Superuser and it wants to update binary.
I think I have the right zip but it has bricked/bootlooped my phone twice.
Can someone advise please
What rom you use? And why you don't use Magisk?
I just had this problem with mine, download the full flashable zip from Chainfires site. Flash it in recovery, but make sure to manually mount the system partition. Once I did this mine booted correctly.