I just tried to install busybox, but without any success. Whenever I try to install it, my phone just reboots.
I tried the unbezahlter by jrummy as well as Stephen. Both without success.
Am I missing something?
BTW: I already remounted the system partition r/w using the jrummy installer.
dabrain42 said:
I just tried to install busybox, but without any success. Whenever I try to install it, my phone just reboots.
I tried the unbezahlter by jrummy as well as Stephen. Both without success.
Am I missing something?
BTW: I already remounted the system partition r/w using the jrummy installer.
Click to expand...
Click to collapse
Stock kernel enforces write protection on the /system partition, even after attempting to remount rw. A solution is to install busybox via a flashable zip in TWRP/CWM recovery.
Thx, that worked.
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.
____________________________________
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
Hi,
I'm trying to root a recent Mediatek arm64 Lollipop ROM and get that not having a patched recovery is a real problem
But I Have a Factory ROM, with scatter file. So I can readback/reflash /system with flashtools.
This make me think I can root the ROM using a shell script after mount /system on a Linux (Ubuntu) PC replicating, at last, part of what SuperSU install script do.
I'll glad to read others ideas about that and what maybe the install method:
- Do a preroot work, reflash and install supersu from Google Play
- Do a full root work installing supersu in /system/app and let SuperSU autocheck finish it at first boot after reflash.
Thanks in advance,
--
Josemi
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
swaderade said:
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
Click to expand...
Click to collapse
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
TonikJDK said:
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
Click to expand...
Click to collapse
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
swaderade said:
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
Click to expand...
Click to collapse
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Since checking mount system does nothing, I went into Advanced > Terminal and did an `rm -rf GoogleHindiIME` and still can't edit the hosts file.
swaderade said:
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
Click to expand...
Click to collapse
I mount in twrp. Delete hindu and korean with the file manager in twrp. Reboot, install adaway and it works. I have never manually edited it.
No, the system mount in twrp does not stick on reboot. Mounting system with systemless root is tricky as I understand it. So I just avoid it.
You can't mount system as rw in a booted Android system unless you have a permissive kernel, and you should not have a permissive kernel.
Had the same problem and didn't want to remove things from /system. You can follow the steps here: http://forum.xda-developers.com/showthread.php?t=3266107
Systemless root on 6.0.1 - How to edit build.prop
Sent from my Nexus 6 using Tapatalk
Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.
marcelser said:
Hi,
I'm running CyanogenMod13 on my galaxy S4 with TWRP 3.1.1.0 and I wanted to flash XPosed. The xposed page says that it's only compatible with SuperSU so I installed latest Stable SuperSU 2.82 and deactivated root access on CM13 in developer options. Then I tried flashing Xposed framework zip but it complained about /system beeing a read-only file system and I realized that TWRP didn't ask me anymore if I want read-only file system (which it always did before I installed SuperSU) anymore. Looking into "Mount" I see that "system" is not mounted by default but also making a checkbox there doesn't change anything even if "Mount system read-only" is not checked. BTW: Do I have to apply the mounts somehow or is activating the "checkbox" actually enough. Maybe my problem is just that system is not mounted r/w which is my current guess but I don't know how to mount it r/w now that SuperSU is installed.
Then I though, ok if mounts are incorrect in TWRP let's use FlashFire. So I selected to mount system r/w in option for flashing and started the flash. Again even if I selected mount system partition r/w flashfire reported read-only file system. I also tried downgrading to SuperSU 2.79 but same effect.
What the hell is going on since I flashed SuperSU. Is my root now partially broken? The Apps all are working fine, it's just modifying system partition is somehow not possible neither in TWRP nor FlashFire....
Any help or insight will be greatly appreciated.
Click to expand...
Click to collapse
Try my SuperSU systemmode from here.
Thanks for the link and it also gave me hint what to google for. It seems that my SuperSU is running in systemless mode, so I would need Systemless Xposed too. Unfortunately this also requires Magisk to be installed and Magisk doesn't work with adoptable storage which I can not live without. So I will give your SuperSU version a try and run it in System Mode and try to install official xposed too. Hopefully this works.
Edit:
I had a hard-time switching from systemless mode to system mode cause you have to completely unroot and restore the patched boot image fully (just un-rooting and restoring doesn't do the trick) fortunately I had a nandroid backup from prior to rooting with untouched backups of "boot" and "system" which I could restore. Finally I was able to install the system mode SuperSU (although I didn't use your package, but created a .supersu file with SYSTEMLESS=false) and flashed it.
This now enabled me to run latest Xposed in system mode which was failing when trying to flash in systemless mode. I would have needed magisk (which is incompatible with adoptable storage) to run it systemless. I tried using the old 86.2 systemless xposed but that always resulted in a boot loop whenever I activated one of the xposed modules). Now it's working fine., Thanks for the hint ho led me find out what system mode and systemless really is.
So actually my problem is solved, just couldn't find out how to edit the thread title....