i change the title becouse i want to see if somebody have my problem
and because I would like to solve a problem I have with the last
script of zeppelinrox and I need someone with gingerbread
that test them with me
i see that some scripts don't work at boot from the init.d folder
like some of domscript because they don't change anything in the corrispettive
files
i'm on a modifield stock and last kernel of raphael baugis
now i tested the script of zep the b34st but when i reboot sometimes
stuck in bootlogo and after pull out battery sometimes
reboot and i have 100supercharger
i did a logcat at reboot but the first whil stuck was empty
another recognize an error about sdcard but in 3 minutes of logcat
only 20lines of mssages
this is the thread http://forum.xda-developers.com/showthread.php?t=991276&styleid=19
and this is the script http://forum.xda-developers.com/showthread.php?p=39519682#post39519682
if someone test it tell me if had problem
thanks men
angel.sea said:
why some scripts don't work at boot from the init.d folder?
i see that in the script of v6 zep say that don't delete the comments
otherwise the script does not work
Click to expand...
Click to collapse
Which scripts didn't work?
Can you name them?
iamareebjamal said:
Which scripts didn't work?
Can you name them?
Click to expand...
Click to collapse
some script of dominic like for example 94tweaks
95..,96...,and 97vm_management...
their files are not changed
I think you're asking about init.d support. If the kernel (you can also directly patch the ROM) doesn't have init.d support, scripts in etc/init.d won't be run automatically. Simple as that.
GermainZ said:
I think you're asking about init.d support. If the kernel (you can also directly patch the ROM) doesn't have init.d support, scripts in etc/init.d won't be run automatically. Simple as that.
Click to expand...
Click to collapse
now i m on last raphael kernel that support init.d
script 00zram work,darkyzipalign even,but i see that
all tweaks that use the command echo don't change
anything....and i ask me why?...
Ynt: script
angel.sea said:
now i m on last raphael kernel that support init.d
script 00zram work,darkyzipalign even,but i see that
all tweaks that use the command echo don't change
anything....and i ask me why?...
Click to expand...
Click to collapse
Download "Pimp my rom" from play store and check if your phone has init.d support. If not eneble it using commands in program.
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
ChelebiTech said:
Download "Pimp my rom" from play store and check if your phone has init.d support. If not eneble it using commands in program.
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
Click to expand...
Click to collapse
I know that my kernel supports init.d infact some scripts are loaded
Ynt: script
angel.sea said:
I know that my kernel supports init.d infact some scripts are loaded
Click to expand...
Click to collapse
Scripts loaded in order (by name) and if some script in the end (99script) then it might override the first ones. Try to compare the scriptings to remove the unwanted ones...
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
ChelebiTech said:
Scripts loaded in order (by name) and if some script in the end (99script) then it might override the first ones. Try to compare the scriptings to remove the unwanted ones...
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
Click to expand...
Click to collapse
i see all script and the set that no work there aren t in the other
...i ve symlink all applet in system/xbin,i ve symlink busybox
in system/sbin i ve busybox in /sbin and in system/xbin...mmmm
i don't know what don't work....
Ynt: script
angel.sea said:
i see all script and the set that no work there aren t in the other
...i ve symlink all applet in system/xbin,i ve symlink busybox
in system/sbin i ve busybox in /sbin and in system/xbin...mmmm
i don't know what don't work....
Click to expand...
Click to collapse
Did you check the scripts in init.d folder? I was talking about them sometimes scripts conflict each other...
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
ChelebiTech said:
Did you check the scripts in init.d folder? I was talking about them sometimes scripts conflict each other...
S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
Click to expand...
Click to collapse
yes
angel.sea said:
yes
Click to expand...
Click to collapse
Can you post the list of scripts which are workin, and the ones wich arent working? As you give little information, no one can help.... (i think)
ChelebiTech said:
Can you post the list of scripts which are workin, and the ones wich arent working? As you give little information, no one can help.... (i think)
Click to expand...
Click to collapse
http://www.mediafire.com/?xfb1msfxrje48ui here there are the scrript
and 94tweaks,95touch,96vm_management,97internet_tweaks don`t work
91darkyzipalign,92sqliteoptimize work works and 93 and 98 i thik work becouse
someting change in my phone thanks
angel.sea said:
http://www.mediafire.com/?xfb1msfxrje48ui here there are the scrript
and 94tweaks,95touch,96vm_management,97internet_tweaks don`t work
91darkyzipalign,92sqliteoptimize work works and 93 and 98 i thik work becouse
someting change in my phone thanks
Click to expand...
Click to collapse
What exactly do you mean by "don't work"? How are you checking?
GermainZ said:
What exactly do you mean by "don't work"? How are you checking?
Click to expand...
Click to collapse
i see that the values in the file that the script had to change
remained those of the stock ...
instead about the tweak of touch this isn o corresponding file in the phone
another thing man
i tried the b34st of zep but i stuck on bootlogo
because it detected a bootloop but in this case
the files log are empty....script don' t work so
don't tell me anything about the error
this only with biuld.prop mode with local instead
don't supercharge the launcher
in the driver i chose superminfree value, soft rock,and sd tweaks
sometimes work fine
do you have same problem?
Related
Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
frz said:
Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
Click to expand...
Click to collapse
found it
http://forum.xda-developers.com/showthread.php?t=1017291
frz said:
Request: any way to get init.d on Stock rom without using CF Root..Its just that ive tried the CF Root & always get SOD...
Ive rooted my phone using upd_1...but i need init.d to run different tweak scripts
will super1click root give me init.d?
Hope ive posted in the right section
Click to expand...
Click to collapse
thanks for it
frz said:
found it
http://forum.xda-developers.com/showthread.php?t=1017291
Click to expand...
Click to collapse
This won't work for Galaxy Ace, because the scripts in that thread refer to some Motorola scripts that are not present in Ace (/system/bin/mot_boot_mode).
Does someone know of a script that gets executed at boot in a Galaxy Ace stock rom? If so, maybe it could be used in the same way as mot_boot_mode for Motorola Droid, and get an executable /etc/init.d in our stock Galaxy Aces...
Just have a look at the "!Autostarts - Enable init.d on Stock ROMS.sh" script. It is very straightforward.
Juanma.
I would really be interested in this. Anyone? Care to shed some light on this little issue?
Basically you have to add this into the init.rc file (after creating manually the init.d folder of course):
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
Click to expand...
Click to collapse
=> an example of usage; or just google "busybox run-parts"
It is the same method which CF-Root also uses. So you still have the option to study the CF-Root way and will learn some more tricks on the way. ...
^^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Android kitchen has that feature
Herpderp Adreno + Tegra.
I found this post here had a possible workaround: http://forum.xda-developers.com/showpost.php?p=20134361&postcount=3
Bakuron said:
I found this post here had a possible workaround: http://forum.xda-developers.com/showpost.php?p=20134361&postcount=3
Click to expand...
Click to collapse
andy572 said:
3. answer is some wrong:
you doesnt need to cook a custom rom, you only need the adb (android debug bridge) to "speak" with your phone:
...
Click to expand...
Click to collapse
That's what she said. ...
^^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tossan said:
Basically you have to add this into the init.rc file (after creating manually the init.d folder of course)
Click to expand...
Click to collapse
So I take it it is not as simple as browsing with Root Explorer, finding the file and adding it. If not, could you tell me how. Can I do it using the terminal emulator app rather than connecting phone to PC and using cygwin? Thanks
tossan said:
That's what she said. ...
Click to expand...
Click to collapse
Sorry, I didn't read your post before I posted. You explained it even simpler so thanks
Gizmotech said:
So I take it it is not as simple as browsing with Root Explorer, finding the file and adding it. If not, could you tell me how. Can I do it using the terminal emulator app rather than connecting phone to PC and using cygwin? Thanks
Click to expand...
Click to collapse
I'm really not sure it's possible. But regarding 'in-phone script writing' Pyronia's just started a thread here on it that you could possibly raise the issue in: http://forum.xda-developers.com/showthread.php?t=1476400
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Gizmotech said:
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Click to expand...
Click to collapse
Rest of that thread has a suggestion on testing if its working forum.xda-developers.com/showthread.php?p=20134361#post20134361
I think permission of init.d is rwxr-xr-x. Check this thread here forum.xda-developers.com/showthread.php?t=1390093
Gizmotech said:
Thanks. I tried to extract using the adb pull command to desktop but kept getting permission denied. So I managed to change permission on init.rc and send it via bluetooth to my desktop. I edited the file and put it back in via bluetooth to sd and then used root explorer to move back the file to root and changed back to the original permission of the file. Before I did this, I manually created the init.d folder. What permissions do I set the init.d folder? Do I set it to rwxr-xr-x like the other folders inside /etc? Also how do I know or test that the script is enabled and that it is functioning properly as it should?
Click to expand...
Click to collapse
Which script? Post the link here...or u open the script then type the command on terminal to check if the script working..
regards,
•ƒγяύs ργяσ™•
pyronia said:
Which script? Post the link here...or u open the script then type the command on terminal to check if the script working..
Click to expand...
Click to collapse
Basically, I mean how would I know if init.d is activated and any scripts I put in is actually working. After all I created init.d folder manually. What command do I type in adb shell to see if scripts are working?
Can someone help me troubleshoot this please. I have put scripts in the init.d folder but see no difference. I followed the method on this thread to enable init.d. I don't notice any difference after putting any scripts such as lagfree, turboboost or even the keylight one.
Gizmotech said:
Basically, I mean how would I know if init.d is activated and any scripts I put in is actually working. After all I created init.d folder manually. What command do I type in adb shell to see if scripts are working?
Click to expand...
Click to collapse
Sent me the script then i show u how to check
regards,
•ƒγяύs ργяσ™•
Gizmotech said:
Can someone help me troubleshoot this please. I have put scripts in the init.d folder but see no difference. I followed the method on this thread to enable init.d. I don't notice any difference after putting any scripts such as lagfree, turboboost or even the keylight one.
Click to expand...
Click to collapse
Which thread actually?
regards,
•ƒγяύs ργяσ™•
Init.d support ? Not without CF-ROOT
Herpderp Adreno + Tegra.
Well I thought this thread was about init.d on stock rom without CF-Root.
Before you flash a custom roM that is tweaked or modified,
double check script,
some script are not modified to run
some script are incompatible for our rom/device
some script are just duplicates,.. this is cause by adding too many scripts
where in some commands are just the same, this will cause same scripts not to run.
Course, so
Greets!
question...
What if the tweaks in init.d have the same number?
amao10 said:
What if the tweaks in init.d have the same number?
Click to expand...
Click to collapse
that was also my question before.. i did a research and found out that even 2 ore more scripts had same number in order it would work.. for EX: 00banner & 00cleaner
it would be read as 00b to run first before 00c.
i have been messing with init.d for rooted/stock rom t230/nu and i have come up with a modified version of this >> http://forum.xda-developers.com/showthread.php?t=1912504
INSTRUCTIONS:
Flash the attacthed zip in twrp and reboot...
HOW DO I KNOW IF IT WORKED?
in root browser goto /data/local/tmp/ and if there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
if the file is not present something went wrong? please let me know if it went wrong for you an i will fix it..
dont forget to hit thanks and also credit the @jamesst20 in the above link...
Ill give it a go.
Sent from my SM-T230NU
BookCase said:
Ill give it a go.
Sent from my SM-T230NU
Click to expand...
Click to collapse
let me know how it goes as i have only tested on my device... thnx
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
g_ding84 said:
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
Click to expand...
Click to collapse
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Inside 4ndroid said:
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Click to expand...
Click to collapse
Let me if your still having trouble with root afterwards.
g_ding84 said:
Let me if your still having trouble with root afterwards.
Click to expand...
Click to collapse
oh and in your rom it seems we cant update the su binary and have to flash an updated binary seperetely from within recovery.. i found a work around and now when i flash my rom it says binary needs updating an now in my rom the normal method works and alakasm success
if you need me to explain further pm me an i will go through how i managed it..
In the rom that you're working on is based on CyanogenMod or this stock?
on the other hand just flash this file in Stock T230XXU0ANK3'll see that this is
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
riotaruna said:
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
Click to expand...
Click to collapse
or you could just simply flash the file file in the OP takes alot less time an is simple an staight forward lol..
File is gone
Hi i just created this zip to install init.d on our phone (G530H)
For those who dont know what is the "init.d" its just a folder on the system where you can put some scripts and will run everytime you start the phone, its usefull to clean some cache, get better performance, zipalign etc. theres a lot of scripts on the web but i dont have time to test all of them so, heres a zip to install this folder, it includes the zipalign binary, tested and fully working, you can also google some scripts, test them and share the results with us
Flash it on cwm or twrp and enjoy
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Humberto.Ortega said:
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Click to expand...
Click to collapse
then... How do this worked?
Dam7lc said:
then... How do this worked?
Click to expand...
Click to collapse
I think this flashable zip has already enabled init.d support in stock kernel. I searched how to enable this support and I found we have to install the file "install-recovery.sh" in system/etc. I download your zip file and I saw that this file is present...
So this zip file doesn´t contains only script, but enable the init.d support for the stock kernel :highfive:
We can check this in /data/local/tmp...there should be a txt file there named "init.d_log_test.txt"
Sorry my mistake
I'll flash it and report later....
Thanks man!!
PLEASE MAKE ONE FOR G530P to enable gsm
To my speculations it seems the g530p is no different from the g530 variants p/h/t/t1 and the others as they all have the same qualcomm baseband but as the cdma feature is enable and the others are lock can you gather a team and make this possible to create a baseband or modem that edit these fields and enable gsm/umts or any other bands to work globally as well as the init.rd
thanks
Resolution on post #10, in post #11 a second resolution and on post #12 the confirmation.
I need a init.d script to run or execute a service that is on system/bin
Is this possible?
Which commands to use?
I researched a lot, and I do not find anything about it.
The file name is jellyservice.
Jellyservice is a normal service that need to be running before run a app, without that, the app does not run.
I know that:
1. The jellyservice is presented on stock rom and the stock rom use init.rc to call the jellyservice at boot, and i can change the init.rc by change the boot.img (unpack, change, repack), but i wanna to be able to run it on any device wit any kernel, and don't wanna to change it kernel for it rom.
2. I can use SManager to run the file on boot. but i don't wanna to need a app just init.d, init.d is already implemented and working on almost every custom rom, so I put the init.d file on a zip that flash the apk, libs etc, and no more app or config is need.
Thanks.
baybutcher27 said:
I need a init.d script to run a service that is on system/bin
Is this possible?
Which commands to use?
I researched a lot, and I do not find anything about it.
The file name is jellyservice.
Jellyservice is a normal service that need to be running before run a app, without that, the app does not run.
I know that:
1. The jellyservice is presented on stock rom and the stock rom use init.rc to call the jellyservice at boot, and i can change the init.rc by change the boot.img (unpack, change, repack), but i wanna to be able to run it on any device wit any kernel, and don't wanna to change it kernel for it rom.
2. I can use SManager to run the file on boot. but i don't wanna to need a app just init.d, init.d i already have implemented on rom, so I put the init.d file on a zip that flash the apk, libs etc, and no more app or config is need.
Thanks.
Click to expand...
Click to collapse
Is this what you are looking for, or I am missing something?
http://forum.xda-developers.com/showthread.php?t=1933849
And this, which is more up to date:
http://www.xda-developers.com/init-d-support-for-any-rooted-phone/
Ciuffy said:
Is this what you are looking for, or I am missing something?
http://forum.xda-developers.com/showthread.php?t=1933849
And this, which is more up to date:
http://www.xda-developers.com/init-d-support-for-any-rooted-phone/
Click to expand...
Click to collapse
No you did not read what I wrote.
As I said, i wanna a script of init.d that runs or execute a file, i already have init.d working...
baybutcher27 said:
No you did not read what I wrote.
As I said, i wanna a script of init.d that runs or execute a file, i already have init.d working...
Click to expand...
Click to collapse
Sorry, I was assuming you could find help there. By the way, you should be able to do this just by using a script like:
#!/system/bin/sh
-Give permission
/path/jelliservice
Then place it in init.d or write a specific script for init.d to run the above one.
http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Sorry if there's a bigger obstacle I'm not aware of.
Ciuffy said:
Sorry, I was assuming you could find help there. By the way, you should be able to do this just by using a script like:
#!/system/bin/sh
-Give permission
/path/jelliservice
Then place it in init.d or write a specific script for init.d to run the above one.
http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Sorry if there's a bigger obstacle I'm not aware of.
Click to expand...
Click to collapse
No is all good.
but??? that willl run the service, or just give a permission.
I don't really know much about init.d script and the web does not help in that thing i wanna.
i'm implemented it now to see what that script does. :good:
baybutcher27 said:
No is all good.
but??? that willl run the service, or just give a permission.
I don't really know much about init.d script and the web does not help in that thing i wanna.
i'm implemented it now to see what that script does. :good:
Click to expand...
Click to collapse
Oh, so you are just asking for help with the actual script, fine. See if you can figure it out yourself from that post, I'm trying to build an easy example right now. I seem to not have this jelliservice you are talking about, maybe you can give me a few more insights about this.
Ciuffy said:
Oh, so you are just asking for help with the actual script, fine. See if you can figure it out yourself from that post, I'm trying to build an easy example right now. I seem to not have this jelliservice you are talking about, maybe you can give me a few more insights about this.
Click to expand...
Click to collapse
ok.
i tested that you post doesn't do what i need.
i have this on init.d to now if it works.
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt
so i change the "done" of the last line to wherever and it time i reboot it change to wherever i wrote.
so init.d is working fine.
The jellyservice is a service that only exist on motorola stock rom on devices that have dedicated hardware of DTV.
it is started by i .rc file:
init.mmi.dtv.rc
and the content of that .rc is:
Code:
on boot
# DTV feature
service dtv-jelly /system/bin/jellyservice
class main
user system
group system audio camera graphics inet net_bt net_bt_admin net_raw sdcard_rw
iknow that is possible to implemented that .rc on any device by add it to the kernel or boot.img but it will be need to do on any rom and that is allot of work and will be impossible.
so i have created a tread to give support for that DTV to any custom rom, and i wanna to make a more completed .zip to the app.
see the thread here
baybutcher27 said:
ok.
i tested that you post doesn't do what i need.
i have this on init.d to now if it works.
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt
so i change the "done" of the last line to wherever and it time i reboot it change to wherever i wrote.
so init.d is working fine.
The jellyservice is a service that only exist on motorola stock rom on devices that have dedicated hardware of DTV.
it is started by i .rc file:
init.mmi.dtv.rc
and the content of that .rc is:
Code:
on boot
# DTV feature
service dtv-jelly /system/bin/jellyservice
class main
user system
group system audio camera graphics inet net_bt net_bt_admin net_raw sdcard_rw
iknow that is possible to implemented that .rc on any device by add it to the kernel or boot.img but it will be need to do on any rom and that is allot of work and will be impossible.
so i have created a tread to give support for that DTV to any custom rom, and i wanna to make a more completed .zip to the app.
see the thread here
Click to expand...
Click to collapse
You are right, it's not easy to test this out because of default .rc hardcoded into kernel... in order to do this you would have to edit .rc to run that service that runs userinit.sh... Have you already done this? And, are you able to start the service manually?
Ciuffy said:
You are right, it's not easy to test this out because of default .rc hardcoded into kernel... in order to do this you would have to edit .rc to run that service that runs userinit.sh... Have you already done this? And, are you able to start the service manually?
Click to expand...
Click to collapse
i didn't try implemented that .rc on boot.img, that is too much work, and need to be done on it kernel or rom update, but yes can be done.
The file is just like any other executable, just like a .sh or any file you can execute using a app that can execute files like, root browser or SManager.
all the process to run the file is on the thread i just post.
The thing is i already know how to run it via app, but i don't wanna to stop there i wanna to run it via init.d because is a very simple way, but very difficult to find the commands.
Exists any command on init.d that can run a file commands like, run, execute, open or start ?
any of those work? and how to use they?
have any website that have all the command available on init.d?
Hey, you can run a binary from sh by just invoking its path, for example:
Code:
#!/bin/sh
/system/bin/jellyservice
The proccess will spawn with UID 0 (root)
You can change that if you have a good root binary by doing this:
Code:
#!/bin/sh
su system -c '/system/bin/jellyservice'
If you're using supersu I think you have to enable root at boot (Look at the application settings)
baybutcher27 said:
i didn't try implemented that .rc on boot.img, that is too much work, and need to be done on it kernel or rom update, but yes can be done.
The file is just like any other executable, just like a .sh or any file you can execute using a app that can execute files like, root browser or SManager.
all the process to run the file is on the thread i just post.
The thing is i already know how to run it via app, but i don't wanna to stop there i wanna to run it via init.d because is a very simple way, but very difficult to find the commands.
Exists any command on init.d that can run a file commands like, run, execute, open or start ?
any of those work? and how to use they?
have any website that have all the command available on init.d?
Click to expand...
Click to collapse
so i resolve this :silly: :laugh: :victory:
after writing I read, and is so lame.
if the file is just like any other executable way not put it in the init.d folder?
and i put, rename to 99jellyservice
and the init.d run it and the apk that need that file to be running before you open it work.
@Ciuffy
Thanks you help me to find a way...
nagalun said:
Hey, you can run a binary from sh by just invoking its path, for example:
Code:
#!/bin/sh
/system/bin/jellyservice
The proccess will spawn with UID 0 (root)
You can change that if you have a good root binary by doing this:
Code:
#!/bin/sh
su system -c '/system/bin/jellyservice'
If you're using supersu I think you have to enable root at boot (Look at the application settings)
Click to expand...
Click to collapse
the 1° option work perfectly!, but i use like this
Code:
#!/system/bin/sh
/system/bin/jellyservice
i think doesn't make a difference.
Thanks man I will use your way, is better that my. :good:
baybutcher27 said:
the 1° option work perfectly!, but i use like this
Code:
#!/system/bin/sh
/system/bin/jellyservice
i think doesn't make a difference.
Thanks man I will use your way, is better that my. :good:
Click to expand...
Click to collapse
Yeah basically the only difference is that Android has no /bin/sh but /system/bin/sh. I though about just putting that there honestly but I couldn't get any of this working on my cyanogenmod so I was trying to figure out why >.>, but I'm probably missing something.
Anyway, glad I could help!