Related
Hi and to the case...
Everything was ok until today. I'm on JVP / Semaphore 1.3.0a with some scripts in init.d folder like ramscript. I don't really know what could happened, but scripts are no longer working. When I try to load them manually via script manager most of them respond "permission denied" or "are you root?". Ofc I'm root
I tried reinstalling busybox, tried delete it and reinstall the kernel (which have it's own version of busybox). Busybox is in the /sbin directory installed by kernel. When i try to install it (1.6.2) in other directory - /system/xbin ; /system/bin it give the same result - scripts not working.
If anyone could help I'll be grateful.
Tried Galaxian GT kernel few minutes ago with same result - scripts can't be executed.
Check the permissions of the scripts. Change it to rwxrwxrwx.
Also uninstall all extra version of busybox. Semaphore kernel has an embedded busybox version.
stratosk said:
Check the permissions of the scripts. Change it to rwxrwxrwx.
Also uninstall all extra version of busybox. Semaphore kernel has an embedded busybox version.
Click to expand...
Click to collapse
Thank you for reply.
Double checked that, permissions are ok. Busybox is only installed by kernel in /sbin. Scripts are not running and I srsly don't know why. Till today everything was fine
nozerogravity said:
Thank you for reply.
Double checked that, permissions are ok. Busybox is only installed by kernel in /sbin. Scripts are not running and I srsly don't know why. Till today everything was fine
Click to expand...
Click to collapse
What did you change today?
stratosk said:
What did you change today?
Click to expand...
Click to collapse
That is very good question!
I didn't change sh#$, excuse my language. If I think about it... I only installed Titanium Backup Activator (needed root who knows for what). I wanted to test Pro features before buying cuz TB is expensive, wanted to know if I really need the Pro features.
Maybe that activator did something? But everything beside that works. I'm so confused. I only know one thing... I will never try pirated apps again :/
TB has his own busybox (1.18.4). But it should not interfere with Semaphore ones (it does not on my phone).
Try to delete this file:
/system/xbin/busybox
It should solve the problem.
Btx, you can use last version of semaphore, it's compatible with JVP.
darckengel said:
TB has his own busybox (1.18.4). But it should not interfere with Semaphore ones (it does not on my phone).
Try to delete this file:
/system/xbin/busybox
It should solve the problem.
Btx, you can use last version of semaphore, it's compatible with JVP.
Click to expand...
Click to collapse
Thank You for reply.
Will try after work. And thanks for the headsup on new version. With the last one I have ... yeah, problem with scripts, so I sticked to 1.3.0a.
Busybox issue. Install busybox installer and install 1.17.x in /xbin. Remove all other instances of busybox and it'll work. Make sure the permissions of the scripts in init.d is rwxr-xr-x.
pikachu01 said:
Busybox issue. Install busybox installer and install 1.17.x in /xbin. Remove all other instances of busybox and it'll work. Make sure the permissions of the scripts in init.d is rwxr-xr-x.
Click to expand...
Click to collapse
Thanks. Will try that also and I will post the results.
Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?
jodvova said:
Im on Android M preview 2 with Desparis 3.3 kernel, rooted.
I would like to update build.prop and change user -> userdebug.
Before on Lollipop all I had to do is remount /system in rw and change the file.
Android M doesn't allow me to remount /system in rw.
adb push fails to overwrite the file.
Any solutions please ?
Click to expand...
Click to collapse
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Thanks! At least it's one possible solution !
david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.
jodvova said:
Actually, can you elaborate how do you do it ?
I've just tried booting into TWRP, then connected the phone to PC, did adb push of changed build.prop into /system, reboot the phone and realized that the phone still has the old build.prop.
Click to expand...
Click to collapse
First in twrp make sure you mount system in the mount menu then you should be able to push and pull. You probably pushed the file nowhere even though I think you should've got a error message. I pulled the build.prop straight from twrp edited it then pushed it right back. Did it for the tethering hack. ? ?
david279 said:
I dont think you can write to system at all anymore, even with root. I do it all in recovery for right now.
Click to expand...
Click to collapse
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.
simms22 said:
sure you can. all i use is root explorer. i change what i need, save it, then reboot for it to take affect. works every time.
Click to expand...
Click to collapse
I didn't think write to system was working in the M builds. Must be something wrong with his root method.
david279 said:
I didn't think write to system was working in the M builds. Must be something wrong with his root method.
Click to expand...
Click to collapse
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you
simms22 said:
maybe. im using despair and sometimes elementalx kernels. does everything else root work for you? all is working here.
edit.. i should ask him, not you
Click to expand...
Click to collapse
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.
jodvova said:
Root works great in all apps.
The only problem I have is with RO system. Before M I would use ES explorer to modify and save build.prop and Android Terminal to remount system as RW. But it doesn't work like that anymore in M.
Ive never tried root explorer.
Click to expand...
Click to collapse
it works exactly like it did before over here. and ive manuslly changed my build.orop several times already.
I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.
KnifeSkills said:
I'm on Preview 2, rooted, Despair kernel 3.3.
Still confused as to how to enable mounting /system r/w from within Android and not TWRP. Trying FX file explorer as well as Terminal Emulator with no success. I have Busybox installed and under Applet Manager it shows the "Mount" applet as installed and symlinked to /system/bin/toolbox.
Click to expand...
Click to collapse
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.
prdog1 said:
Haven't tried M as it buggy but have used Root Explorer the grand father of file explorers on everything since TBolt.
Click to expand...
Click to collapse
root explorer since 2009 here
simms22 said:
root explorer since 2009 here
Click to expand...
Click to collapse
Root Explorer FTW. Always works and same file system as shows on PC.
Well Root Explorer wasn't the answer, surprisingly enough haha...
Needed insecure boot.img obtained here flashed with help from this thread, with further reading here for better understanding or doing it yourself.
Also I apparently forgot that adbd insecure by chainfire exists until just now, which could have potentially been another solution.
So I flashed 6.0, HellScore's newest kernel that disables R/W protection (b7-M).
All my other root apps are working however Layers is not. Am I missing something? Cause it seems like Google pulled a fast one and yanked RRO out from the final build.
I havent' been able to get Layers to work on any of the M builds. It acts like it's applying the layers but the reboot command from within the app doesn't reboot the phone, and no layers are applied after a manual reboot. All the white is blinding me!
Got Layers working guys.
Gotta have BusyBox as well as enough space on the /system partition.
Peylix said:
Got Layers working guys.
Gotta have BusyBox as well as enough space on the /system partition.
Click to expand...
Click to collapse
...and also a Kernel that allows system r/w which some don't at the moment.
Hey mate how did you change the space on /system partition?
Im trying to install adaway but no space it says
Peylix said:
Got Layers working guys.
Gotta have BusyBox as well as enough space on the /system partition.
Click to expand...
Click to collapse
TheLoverMan said:
Hey mate how did you change the space on /system partition?
Im trying to install adaway but no space it says
Click to expand...
Click to collapse
use titanium backup and convert non essential google apps to user apps.
TheLoverMan said:
Hey mate how did you change the space on /system partition?
Im trying to install adaway but no space it says
Click to expand...
Click to collapse
Debloat the partition by trashing pre installed GAPPS. I got rid of apps like Keep, Slides, Docs, Earth, Messenger, Keyboard languages other than English, and a few others. That cleared up enough room for Layers and Adaway for me.
You can manually rid of these using a file explorer, or download a system uninstaller app.
Hope this helps.
danarama said:
...and also a Kernel that allows system r/w which some don't at the moment.
Click to expand...
Click to collapse
True, I figured my OP would cover that aspect. Should have included it with my follow up post. (I am tired, I spent 5+ hours trying to get Layers to work. It all came down to stupid debloatiing of the /system lol)
Peylix said:
True, I figured my OP would cover that aspect. Should have included it with my follow up post. (I am tired, I spent 5+ hours trying to get Layers to work. It all came down to stupid debloatiing of the /system lol)
Click to expand...
Click to collapse
haha. Guess who didn't even read the OP...
Hi @all. Adaway doesn't work for me. It can't copy the host files. I don't know why. Root is okay, checked with root checker. Adaway has permission to write on the storage. Can anybody help me?
OOS Nougat
Crazy32 said:
Hi @all. Adaway doesn't work for me. It can't copy the host files. I don't know why. Root is okay, checked with root checker. Adaway has permission to write on the storage. Can anybody help me?
OOS Nougat
Click to expand...
Click to collapse
Is /system mounted r/w?
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
Is /system mounted r/w?
Click to expand...
Click to collapse
I don't know. How can I check this?
dustin_b said:
Is /system mounted r/w?
Click to expand...
Click to collapse
Solid Explorer shows this:
Crazy32 said:
Solid Explorer shows this:
Click to expand...
Click to collapse
Sorry for new post, but with xda app I can't edit posts and add a picture.
And this for system:
Crazy32 said:
Solid Explorer shows this:
Click to expand...
Click to collapse
That's just for the hosts file. You want to know if /system is mounted rw. If you have an app like terminal emulator, open it and type: mount Then look for /dev/block/bootdevice/by-name/system on /system type ext4. In parentheses it will either have ro (read-only) or rw(read-write).
Also, I don't use Solid explorer but it probably has a way to mount the system rw. Someone else would have to help you with that.
Edit: You would have to be rooted to change permissions with a file manager like Solid.
Sent from my OnePlus 3T using XDA Labs
Download version 3.2 or higher and activate "enable systemless mode" in preferences. Then you won't get that error.
gok90 said:
Download version 3.2 or higher and activate "enable systemless mode" in preferences. Then you won't get that error.
Click to expand...
Click to collapse
Thx, this works
I have a problem too looks like this and it cannot load it... help
Check your host sources, too. Here's what I use.
Heloo the same problem herr tried all means mentioned above no help bad enough i don't see systemless in Adaway 3.3
Image
Solution - go to twrp, go to wipe then advanced wipe, select system and then tap on increase size.
The problem is because the partition has no space left to accommodate files. You will not be able to write host files nor change font via ifont because both files need space ~5mb. Hope this solves your problem.
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
eXtremeDevil said:
So I've been using the LiveBoot module from this post on MM, but today I've updated to Nougat and it does not seems to work. Does anyone knows something about this?
I think the LiveBoot app do work, can anyone confirm?
Thanks.
Click to expand...
Click to collapse
you can get it working pretty easilyg without a module having to be installed, just install it like a normal app on your phone and then put the file it makes after it installs into the magisk.img (while its mounted) in the post-fs-data folder.
It will look like this:
/magisk/.core/post-fs-data.d/0000liveboot
the contents of my working 0000liveboot script is:
#!/system/bin/sh
/system/bin/sh /data/user_de/0/eu.chainfire.liveboot/files/liveboot &
If for any reason the file called is not in that spot, you'll gave to find it manually and change the script to reflect where it is on your particular phone. Possible locations might be /data/user/0/ or /data/data/
Best case is you can just use the 0000liveboot script exactly like I have it. Try that first. If you have no log overlay next boot, you'll have to did where the I installed liveboot app you have is keeping its data and simply change the script so it reflects wherever you find it, then try rebooting again and it should work!
I should mention I'm using v1.60 of chainfire's app
the attachment here is just the script that I know works, just in case anyone wants it.
Sent from my LG V20 using XDA Labs
Thanks, I'll try and tell you. And nice signature by the way haha
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
I installed the app but I can't go further if I don't allow the installation of the script in the system partition, and that's what I'm trying to avoid…
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Didgeridoohan said:
Try the init.d linker module in the Magisk repo (in Downloads in the Manager).
Click to expand...
Click to collapse
How? I don't know exactly what you mean
eXtremeDevil said:
How? I don't know exactly what you mean
Click to expand...
Click to collapse
All the LiveBoot app needs is a working init.d. If your ROM doesn't have that already, the easiest way to achieve this with Magisk is to symlink /magisk/.core/post-fs-data.d to /system/etc/init.d.
I haven't tried it myself, but you should simply be able to install the init.d linker module, reboot, install LiveBoot and then let it do it's thing. Nice and systemless.
Reading your previous posts again I see that the app already has asked to install the script, meaning you already have init.d support. Why not just let it install the script? If you have init.d you don't have to worry about official OTAs anyway and it is very unlikely it'll trip SafetyNet (if that's what you're worried about). Or, just use the above mentioned module.
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
eXtremeDevil said:
OK, I installed the app, let it do it's thing, then moved the script from init.d folder to post-fs-data.d magisk folder, created a symlink back to init.d folder so the app doesn't complain about script not installed (and also to be able to edit its settings), rebooted and it's working again!
Thanks so much for the help
Click to expand...
Click to collapse
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Rhaegar85 said:
Hi,
I am sorry , I am not able to find the init.d folder and post-fs-data folder.could you please guide me with the full path for these.Thank you.
Click to expand...
Click to collapse
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Sent from my ONE A2003 using Tapatalk
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Thanks.Yes, I have. Found the path and managed to create a symlink, still not working. I used sdmaid to move files and Mount the partition and terminal to symlink.I am using MI 5 Gemini with ViperOS 3.1. Can this be done on my device?
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Thanks for your help. Yes, I had the file on that path. It was not working even after moving the 0000liveboot file to magisk/.core/post-data-fs.d. I have now done a clean install of Viper with SuperSU rather than magisk. And now it's working like a charm. I never had the liveboot working with Magisk except for test run. Thanks for your help.
eXtremeDevil said:
You have Magisk installed? The full path is /magisk/.core/post-fs-data.d
Click to expand...
Click to collapse
Hi,
Yes, sorry, I moved the file to magisk/.core/post-fs-data.d, and created a symlink as well, but it was not working. And I really don't want to leave viper or liveboot either, so I installed SuperSU. But can this be done using Magisk? I am using mi5 Gemini, Viper OS 3.1.1. Thank you again.
eXtremeDevil said:
Do you have LiveBoot installed? Does it work on it's own? What do you mean by mounting? I didn't need to mount anything.
The init.d path is /system/etc/init.d.
That's where the liveboot script should place itself once the app installs. That's the first step, do you have it there? Does it work?
Thanks.
Click to expand...
Click to collapse
Ha! Finally it's working now on magisk . I copied the liveboot file in magisk directory and installed init.d linker on magisk. Instead of creating a symlink using terminal, just moved the initlinker.sh file to the original source and Bingo! Thank you very much mate. I almost lost hope using liveboot with magisk. It was possible for you, THANK YOU?
(Magisk 15.1 / init.d enabler v2.2 , LiveBoot v1.6 )
I can also confirm that the Official Liveboot v1.60 from Playstore in combination with Magisk 15.1 works as soon as it finds a working /system/etc/init.d.
The Linker Modul does its job as expected by Didgeridoohan.
The Test Run works perfect.
When i boot up the phone i can see that Liveboot starts, as the screen is flickering shortly in the transition from Boot-Bootscreen and System-Bootscreen (same logo).
But the scrolling liveboot log itsself just shows up for half a second, when the boot screen switches to "home" respective Lockscreen respective the launcher.
From the previous state (SuperSu/Magisk 12) i know thats it is supposed to appear very soon on the screen.
The liveboot option "overlay on top of the boot animation" changes the appearance of that mentioned half second, but not the timing of the appearance.
Any ideas ? Which Logs ?
Thanks, Greets and a happy 2018
Just put the (liveboot) script in /magisk/.core/service.d, works like a charm.
Confirmed !
Now works like expected. Thank you !
Any way to get this to work on pixel 2 xl ? I tried the above and it fails The closest ive gotten so far is the google logo changed to an android one and the test on the liveboot app works.
Im confused I tried all the steps again but from fromflash fire and it failed, but flash fire itself reboots and scrolls the catlog while its flashing. ( think it reboots twice )