Init.d Enabler + Busybox Installer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As name suggest it's simple tool to enable init.d support without custom kernel. Also this tool have option to install busybox.
Requirement : Rooted Note4 (may work on other device but not tested) + Knowledge - why you needs to enable init.d.
Installation :
- Download attached InitD enabler 1.1 apk and install as regular application.
- Before using it make sure you have busybox installed as init.d requires to have busybox. (many custom ROM haves busybox included but stock ROM won't have it.)
- Open application from drawer
- If your device doesn't have busybox then first select to install busybox and reboot.
- Select to enable init.d support and reboot.
Now device should have init.d support. This tool will inject small test script to check init.d is enabled or not.
- Select Test option from application, it will show you status of init.d as floating message. In case status = Working then look for time too, it should match to last boot time of device.
- If you are not sure about busybox and status doesn't show working, you can try Installing busybox and see.
If everything is fine then you can un install application. Also you can delete test script (system/etc/ini.t/ketan) too.
Credits & Thanks : Busybox developer. (If I am not wrong he is Erik Anderson)
What is init.d ?
This is the traditional service management package for Linux, containing the init program (the first process that is run when the kernel has finished initializing¹) as well as some infrastructure to start and stop services and configure them. Specifically, files in /etc/init.d are shell scripts that respond to start, stop, restart, and (when supported) reload commands to manage a particular service.
Click to expand...
Click to collapse
Reserved
Last.
Dr., L8 is already init.d supported or we want to use this tool to enable? Pls advice
joe.sebin said:
Dr., L8 is already init.d supported or we want to use this tool to enable? Pls advice
Click to expand...
Click to collapse
Busybox is Preinstalled on All My ROMs but you need to use this tool for init.d if you need it.
will this let you make stock kernel permissive?
Dmkarkutt said:
will this let you make stock kernel permissive?
Click to expand...
Click to collapse
No. Some mode script requires to run on boot. This will help you in this case.
dr.ketan said:
No. Some mode script requires to run on boot. This will help you in this case.
Click to expand...
Click to collapse
Thanks Doc
for what is init.d ?
ManDone.vRs said:
for what is init.d ?
Click to expand...
Click to collapse
+1 I'd like to know too or is it a case of "If you don't know if you need it, then you don't" ?
Hi my friend. I just installed it as I run a custom kernel but I don't know where I can find the different scrips to use with it ? The most common and interesting one I mean. I know there are many scripts.
Envoyé de mon SM-N910F en utilisant Tapatalk
Custom kernel usually includes init.d support. Anyway of your doesn't have then fine, you can use this but sorry for script as many of mods I do release but myself hardly using it and same here don't know any useful script. xda search surely help you.
Sent from my SM-N910G using xda premium
Does this work with Exynos?
Related
Credits and/or Thanks >>> dsixda/dferreira/jr33/leonnib4/micromod777/pershoot
Source-compiled FroYo-ROM for N1 w/root/su/busybox/deodex. The date/time of AOSP froyo repo sync is listed in zip file name. This is not a "kang"... it is a plain vanilla build with few extras and is basically posted for theming, tweaking, modding, or whatever...
If you want to upgrade the kernel, try flashing one of the pershoot 2.6.35 1.113ghz oc-uv. I use either of his r6 along with a micromod777 theme and my N1 is running fast and stable
white arc reactor bootanimation (apophis906)
apn list (cyanogen)
trackball wake/unlock screen (crimsondr)
tether widget (jmdsdf)
accuweather widget (allows multiple location widgets)
logger app (mnovakjr)
stk.apk (aosp sim toolkit: requires compatable sim)
bash command shell (use terminal or connectbot from market)
apps2sd (darktremor fat32/ext3 partitions)
a2sd basics:
> connect n1 to pc and run adb shell...then run...
# a2sd install
> if you want dalvik cache also on sd...run this next...
# a2sd cachesd
> this is how you check a2sd...
# a2sd check
> to exit adb shell...
# reboot
If you don't have a N1 FroYo radio installed, fastboot flash radio first...before flasing the ROM.
Always do a nandroid backup first then wipe data and caches.
Radio Download >>> 3321c196d8ec1cf748fd20c3c4068520 32.36.00.28U_4.06.00.12_7 radio.img
(Fastboot flash using "fastboot flash radio radio.img")
ROM Download >>> 46c90a4ceaa6316cf314034709f1592a AOSP_Vanilla_FroYo.20100802.112912_signed.zip
Google Apps >>> http://mirror.kanged.net/gapps/
Nice, i'm waiting for a light and "default" rom based on FRF91. Thank you
Boot animations isn't default
sergey.petrushin said:
Boot animations isn't default
Click to expand...
Click to collapse
sorry. i should have posted that i put in the boot animation from the early n1 development phone release. i believe it is also known as the "holiday" boot animation. the asop animation is a simple shimmering light-blue/gray animation of the word "android". if you remove the bootanimation.zip from /system/media, it should boot with the simple stock animation.
WiFi Error
Getting an error when enabling WiFi.
Bohemus said:
Getting an error when enabling WiFi.
Click to expand...
Click to collapse
i'm wifi tethering at the moment with no issue. what is error? i'm sure you did a full wipe first.
Did full wipe, when i turn on wifi it immediately says error.
Will test it tomorrow. If you could pm me a logcat that would be great.
Sent from N1...
Bohemus said:
Getting an error when enabling WiFi.
Click to expand...
Click to collapse
UPD: Same issue here.
two attempts to get author of trackball alert to share mods needed to support his app. no luck getting an answer. this alternative called "BLINK" is a free market app but is limited in its functionality compared to trackball alert:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit/update: trackball alert framework patch now included with pro but still debugging. have sent framework debug to lilhermit and hopefully things get sorted and i can have trackball alert working finally...without having to go back to someone else's tweaked froyo rom.
Bohemus said:
Getting an error when enabling WiFi.
Click to expand...
Click to collapse
sergey.petrushin said:
UPD: Same issue here.
Click to expand...
Click to collapse
download and flash latest pershoot kernel or click here to download.
can someone with a sim that works with the android sim tool kit application please let me know if the stk.apk in this rom is functional?
When ever i try to do the following
- Converting app to user
- Uninstalling system app
- Setting to default installation to internel
I get "SEGMENTATION FAUL"
I am using stock 4.0.4 with extended stock kernel
Any fix for this please:crying:
Do you use version 2.1.2 with older version i got the same error.
XDA Thread: http://forum.xda-developers.com/showthread.php?t=919326
GooglePlay: https://play.google.com/store/apps/details?id=com.buak.Link2SD
skuhn1978 said:
Do you use version 2.1.2 with older version i got the same error.
XDA Thread: http://forum.xda-developers.com/showthread.php?t=919326
GooglePlay: https://play.google.com/store/apps/details?id=com.buak.Link2SD
Click to expand...
Click to collapse
Same Error.:crying:
have you updatet su? (look in superuser app if version is 3.0.3.2)
You can try to flash in cwm su-bin-3.0.3.2-efghi-signed.zip
and the busybox_v1.19.4-wraithdu-CWM_flashable_install.zip
This 2 files reinstall su to v3.0.3.2 and busybox to v1.19.4-wraithdu possible is busybox reinstall is not needed
skuhn1978 said:
have you updatet su? (look in superuser app if version is 3.0.3.2)
You can try to flash in cwm su-bin-3.0.3.2-efghi-signed.zip
and the busybox_v1.19.4-wraithdu-CWM_flashable_install.zip
This 2 files reinstall su to v3.0.3.2 and busybox to v1.19.4-wraithdu possible is busybox reinstall is not needed
Click to expand...
Click to collapse
Where can i find those two flashable zip?
Is busybox necessary?
I don't have busy box
Look at my Post there are 2 attachments, su3.0.3.2 and busybox
download it -> copy to your sdcard -> restart your phone in recovery mode -> install the 2 files with the recovery - restart your phone -> try link2sd
I don´t know if busybox is needed but it is better to install because some other root-apps need it
skuhn1978 said:
Look at my Post there are 2 attachments, su3.0.3.2 and busybox
download it -> copy to your sdcard -> restart your phone in recovery mode -> install the 2 files with the recovery - restart your phone -> try link2sd
I don´t know if busybox is needed but it is better to install because some other root-apps need it
Click to expand...
Click to collapse
Thanks Brother!!
Its ok now:laugh:
"SEGMENTATION FAUL" error is cause by Superuser SU binary....
here FAQ about Link2SD HERE....
Update your Superuser SU binary...it will fixed your problem....
You can update your su binary within the super user app. Load the app and wish right. You will get this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ics wt19i using tapatalk 2
Newer Versions of the su bin causes segmentation fault in other apps on my phone so i let him update/downgrade to 3.0.3.2 which works perfect.
I use ICS Stock ROM on my Mini (ST15i)
skuhn1978 said:
Newer Versions of the su bin causes segmentation fault in other apps on my phone so i let him update/downgrade to 3.0.3.2 which works perfect.
I use ICS Stock ROM on my Mini (ST15i)
Click to expand...
Click to collapse
3.1.1 works flawless on my phone. No problems.
Sent from my ics wt19i using tapatalk 2
Thanks
skuhn1978 said:
Look at my Post there are 2 attachments, su3.0.3.2 and busybox
download it -> copy to your sdcard -> restart your phone in recovery mode -> install the 2 files with the recovery - restart your phone -> try link2sd
I don´t know if busybox is needed but it is better to install because some other root-apps need it
Click to expand...
Click to collapse
Thanks man u
It helped me as well.
Description:
Init.d contains tweaks and scripts that are ran at system startup.
Options & Usage:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved
init.d scripts not listed
Hi there. I noticed there are few more init.d script settings now than that is listed in this thread. Any chance an updated list of all the new init.d settings and what they do? Really appreciate the work you put in cheers.
(or maybe could you point me in a direction to learn what they do? )
Trying ion kernel test 2 makes my coconut stuck on the kernel logo too (LX)
Sent from my WT19i using XDA Premium 4 mobile app
Jerryxmas said:
Hi there. I noticed there are few more init.d script settings now than that is listed in this thread. Any chance an updated list of all the new init.d settings and what they do? Really appreciate the work you put in cheers.
(or maybe could you point me in a direction to learn what they do? )
Click to expand...
Click to collapse
The code for the scripts are all located here: https://github.com/PAC-man/android_vendor_pac/tree/pac-4.4/prebuilt/common/etc/init.d
iurnait said:
The code for the scripts are all located here: https://github.com/PAC-man/android_vendor_pac/tree/pac-4.4/prebuilt/common/etc/init.d
Click to expand...
Click to collapse
Hmm....the link doesn't give a very good explanation about every scripts and what it do.....it just a code of the scripts and it doesn't give any explanation about it....
About the loopy option..
It says to put our launcher name in order to work.
Do we need to put the exact name (as it is in data/app/..) like com.android...apk?
Quick question....is the code merging issue being worked on for theming options as to not be forced to download launchers??
up to date list?
Anyone know where an up-to-date lisr can be found. PAC Rom has waayyy more than just these ones.
Thanks
Piout said:
Anyone know where an up-to-date lisr can be found. PAC Rom has waayyy more than just these ones.
Thanks
Click to expand...
Click to collapse
I would also like to have an updated list on what the things do...
for example what does the battery tweak do?
anyone else with a Nexus 7 (flo) unable to access the init.d menu? I've been unable to access it on every 4.4 PAC build as it comes up saying Settings has stopped. Is this a known problem with Flo builds or...?
Works perfectly fine on my Nexus 5 though.
Full init.d list from august end release
Here's very fresh tweaks list from the HTC Amaze
sometimes my ucoz doesn't work, but it'll be soon
I don't have a clue what exactly (or how exactly) most of them works. But I would like to.
Can somebody of the team post [Explained] thread? Very please.
P.s. As I see, most of them aren't needed for better performance.
city2026 said:
Here's very fresh tweaks list from the HTC Amaze
sometimes my ucoz doesn't work, but it'll be soon
I don't have a clue what exactly (or how exactly) most of them works. But I would like to.
Can somebody of the team post [Explained] thread? Very please.
P.s. As I see, most of them aren't needed for better performance.
Click to expand...
Click to collapse
yeah come on...how its this not documented?
enohand said:
yeah come on...how its this not documented?
Click to expand...
Click to collapse
At the very least there could be a better description under the option.
Like enable sysctl has the description " enable sysctl tweaks at boot", which adds no information. Why not just say "performance tweaks"?
Sent from my SPH-L720 using XDA Free mobile app
I also would prefer a better description. Just making a sentence out of two words does not explain anything. It is not necessary to explain the exact programming. But things how - what does the setting do; is the activation of one interfering with another one; is there, because of interfering, an order in which they should be activated;... - would be really nice.
Need Good Description of New Init.d Setup
Can we please get a good tutorial/description of all the new init.d tweaks on the newest PacMan Rom for the HTC One M8? I am way confused as to what they are all supposed to do. Help!
So any news about a good documentation of the Init.d scripts??
I don't know which ones to enable if I don't know what they do!!
★ - = Activation of support of OTG =-★ and applications for operation with OTG
To be necessary set by TWRP and ROOT
(original post, thx this man BadWolfYe)
1) For activation of support of OTG to set through TWRP archive
2) For switching on and switch-off of support of OTG to install the application
tested 100%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS: If not to disconnect OTG in the application, then in case of connection of a cable to the PC, the MTP mode won't work!
The APP it's from me...........
you dont credit's to me, and renamed the app..................
BadWolfYe said:
The APP it's from me...........
you dont credit's to me, and renamed the app..................
Click to expand...
Click to collapse
The application is not protected from editing and in an open entry is in the Internet
What rights and agreements I did not break!
Your claims without are thorough
Em... Wtf????
Ypu kiding me? Really? All mod and app its me and you really say these?
Wtf?
BadWolfYe said:
Em... Wtf????
Ypu kiding me? Really? All mod and app its me and you really say these?
Wtf?
Click to expand...
Click to collapse
Found your original post, added on it the reference.
Seriously the man, the future, instead of a lot of unnecessary words, just specify the link to your metarials as proofs!
Ok, thanks and sorry for no post the link and words...
Regards
I would really like to thank you for this post and the provided files. You made my day
Doesn't work
Hi,
The apk doesn't ask SuperSu for root permission.
(honor 5c L-51)
How can I fix this?
Thanks and sorry for my bad english.
Thx will try on my new phone
Same issue that @BruugarStalker , the apk doesn't ask supersu for root permission, i'm on a honor 5C L-51 as well.
Somebody has an idea ?
@Zhyrclew Install this package for rooting this device:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip?retrieve_file=1
and there should be have no problem with granting permissions in this app.
@przemas2468
My device is already rooted with supersu, i flashed the ZIP file from the download section of supersu.com (Recovery Flashable.zip -v2.79) on the twrp recovery. (can't post a link sry)
Plus, I already have several apps that have asked and were granted root acces without any problem.
I'll try the version u linked later, but i'm not convinced.
I already flashed the OTG activator with success btw, and if i can't test with any devices the otg function for now, i noticed that despite the malfunction of the otg connect app, the 'USB host check' app now checks the 'android.hardware.usb.host.xml' and 'handheld_core_hardware.xml' as OK, and says that the otg function seems enabled.
I replaced my supersu v2.79 by the v2.65 you linked, and reinstalled the otg connect app, and it worked ! The app have now root access, and I can connect/disconnect normally. Thx !
Then I updated the supersu to the last version, and the otg connect app still work fine. Perfect
Same problem the app doesn't request for root access
[email protected] said:
Same problem the app doesn't request for root access
Click to expand...
Click to collapse
for nougat ,use elite kernel by HassanMirza.
Alright, I just made a custom kernel based on current Android Oreo build 41.3.A.2.234 which enabled root properties and you can flash it by using fastboot method and then, you can install Magisk and also drmfix on TWRP after flashing the custom kernel. Just got an idea to create this custom kernel by editing the rootkernel script and this custom kernel might fix some issues especially the chrome browser turned into "Android Go" mode due to tiny swap partition.
Before installing, make sure that you have current Android Oreo build 41.3.A.2.234 installed on Xperia XZs G8231 or G8232 model and the bootloader must be unlocked first (you will need to perform backup on TA partition first before doing so - I'm really didn't noticed about that part before unlocking my device so don't follow my mistakes by not performing TA partition backup before unlock the bootloader!)
One more thing to remember - DO IT AT YOUR OWN RISK!!!
Download it here:
G8231: [Google Drive link]
G8232: [Google Drive link]
Note: If you did not have current firmware build installed, you can install it by using Xperia Flashtool program. Make sure that you are flashing the right kernel for your device model. You will be not entertained if you ask on how to unlock bootloader and even flashing the custom kernel. You should know the risk of flashing the wrong kernel and you should know how to handle it.
UPDATE: Adding the G8232 custom kernel as requested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great work sir :good:
great work for this and is able to dual sim version ??
Dark Pwince said:
great work for this and is able to dual sim version ??
Click to expand...
Click to collapse
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.
amirzaim said:
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.
Click to expand...
Click to collapse
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?
QPR_FC said:
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?
Click to expand...
Click to collapse
Ok...just flash the G8232 custom kernel which I posted here recently.
amirzaim said:
Ok...just flash the G8232 custom kernel which I posted here recently.
Click to expand...
Click to collapse
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file
QPR_FC said:
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file
Click to expand...
Click to collapse
Probably a few of x-executable files which didn't set its permission for executable: bootimg, busybox, init and even rootkernel.sh itself