Ok..seems that the su access in your terminal emulator is not working well, so I will upload a cwm zip soon...wait for that...
ok thanks
Ok..seems that the su access in your terminal emulator is not working well, so I will upload a cwm zip soon...wait for that...
ok now it works very nice, the failure busybox run-parts was not installed.
Thanks for help
title says it all.
followed the instructions to the letter, console window says successful install.
restarted 4 times. /data/ folder is still empty.
cherry mobile w100.
test.log found in /DATE but init.d folder isn't created on Galaxy tab 7.7, is that ok?
Sent from my GT-P6800 using xda app-developers app
Ok...have you installed busybox with all the applets especially run-parts? Refer to the discussion before this, a user can't get it working because he was lack of run-parts...
Thanks for replying. I used Busybox installer (stephen erickson) smart install function. after installation, applet manager says run-parts is symlinked to: /system/bin/busybox.
is this right or do i have to do something else?
Ok...use the normal install method...as stated there, it is safer and much more effective......and reboot after installing before running the script...
Ok...can you run the script and screenshot the output? And check whether is there any init.d folder in /system/etc, a file named sysint in /system/bin and a file named install-recovery.sh in /system/etc?
ok so this is weird, I was playing around with the terminal, executing run-parts /system/etc/init.d -- it looks like it was executing, but going back to ES Explorer and browsing /data/ folder, it was still empty.
But when i tried to execute
sh /system/etc/init.d/00test
and going back to the /data/ folder, all of these other folders and files(probably created by link2sd) along with the test.log were created right in front of my eyes. am not sure what triggered this but after deleting the test.log and restarting, lo and behold it was re-created.
am trying to delete the test.log again and restart but i am confident that its going to be there when i do.
thank you so much Ryuinferno!
# init.d support
run-parts /system/etc/init.d/
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks. It essentially opens the door to a world of mods only possible through the Init.d process, which in turn is usually only available on custom kernels.
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks. It essentially opens the door to a world of mods only possible through the Init.d process, which in turn is usually only available on custom kernels.
the_scotsman (Moderator Liaison Admin / Moderator Committee / XDA News Writer) said:Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks. It essentially opens the door to a world of mods only possible through the Init.d process, which in turn is usually only available on custom kernels.
# init.d support
busybox run-parts /system/etc/init.d/