[Tool] Init.d with stock Kernel + Busybox Installer - Galaxy Note5 Android Development

Init.d with stock Kernel + 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.
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.
Requirements :
1. Rooted Note5 (Tested on N5 but should work on other similar Exynos like Edge6, Edge6 plus )
2. Knowledge - why you need to enable init.d. Simple way if you have no idea why you need this, it's not for you.
Installation :
- Download attached InitD enabler N5 1.1 apk and install as regular application.
- Open application from drawer - Grant su
- You can see status of Busybox on main page of app. - Init.d requires to have busybox. (many custom ROM haves busybox included but stock ROM won't have it.). 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 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)

tks for share

Thanks for making this, Works great, installs fine and I am able to run my scripts!!! Thanks again Bro

After installing and rebooting when i test it returns %NOTWORKING
Samsung Galaxy Note 5 SM-N920C Stock 6.0.1 Systemless root.

Tamir_Hazut said:
After installing and rebooting when i test it returns %NOTWORKING
Samsung Galaxy Note 5 SM-N920C Stock 6.0.1 Systemless root.
Click to expand...
Click to collapse
If you need init.d then instead use su.d which already activated if you are using systemless root
If you need busybox then look in Note4 development, I have posted busybox for Marshmallow.

dr.ketan said:
If you need init.d then instead use su.d which already activated if you are using systemless root
If you need busybox then look in Note4 development, I have posted busybox for Marshmallow.
Click to expand...
Click to collapse
I installed Busybox from the playstore and universal init.d and now it works.

Related

[SOLVED][Q] V8 Supercharger problem

This is the first time I try V8 Supercharger. I ran the script busybox_v1.19.4_wraithdu--boot_reinstaller_script_v3--installs_every_boot as root in Script Manager and then I rebooted the phone. After that I ran V8_SuperCharger_Alpha_Milestone_Special.sh as root, selected option 6. Balanced 3 Settings {6,8,26,28,30,32 mb} , then option 19 to exit and then i rebooted the phone. After the boot I went into Script Manager, ran the V8 Supercharger script as Root again, and the result is not the one I wanted. The script confirms Launcher is hard to kill but the minfrees values are the current rom's default {6 8 16 36 40 40 mb} and not the wanted {6,8,26,28,30,32 mb}. The settings just don't stick. I've tried to Unsupercharge and reboot the phone then run the script again but I get the same results. I am using Elelinux-7.2-Hero-v3.7. What can I do to make them stick? Am I doing something wrong?
{
"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"
}
Well, before supercharger it, you have to take a look into /etc/init.d to see what scripts elelinux included in his rom (a2sd, cache2cache, mountext - do not touch these) and if you find some scripts like these: loopy_smoothness_tweak, speedy_modified, clean_ram, 99supercharger, edt_tweaks or anything that hasn't to do with a2sd, cache, mountext, you should delete those, reboot your phone and then try to super charge it. I suggest install busybox installer and choose to install a busybox v 1.8.1 because if you have higher, the script will probably create problems.
Cheers!
1ceb0x said:
Well, before supercharger it, you have to take a look into /etc/init.d to see what scripts elelinux included in his rom (a2sd, cache2cache, mountext - do not touch these) and if you find some scripts like these: loopy_smoothness_tweak, speedy_modified, clean_ram, 99supercharger, edt_tweaks or anything that hasn't to do with a2sd, cache, mountext, you should delete those, reboot your phone and then try to super charge it. I suggest install busybox installer and choose to install a busybox v 1.8.1 because if you have higher, the script will probably create problems.
Cheers!
Click to expand...
Click to collapse
From /etc/init.d/ I removed the script for busybox reinstaller 1.19.4 (forgot the name) and the 99supercharger. I've installed busybox 1.18.1, reboot and tried to unsupercharge, reboot, supercharge again with Balance 3, reboot, but the memfreeze values are not changing. The only ones remaining in /etc/init.d/ are 00banner , 01sysctl, 03firstboot , 04modules , 05mountsd , 06mountdl , 10apps2sd , 12compcache , 20userinit . Which are safe to delete?
Edit: I've sent you a PM
Edit2: I installed busybox 1.18.1 again and after that the script worked as it should and the memfreeze values sticked . I think busybox 1.18.1 didn't work the first time.
Thank you !
Leave it as it is because those are script that makes some things in the rom to work. I see you have included 99supercharger script in the zip, you made the zip after you supercharged it again? if so, the script is applying correctly and the values are these:
echo 0,2,4,7,14,15 > /sys/module/lowmemorykiller/parameters/adj;
echo 1536,2048,6656,7168,7680,8192 >
if you want I can provide you a script to push it in /etc/init.d to change those values but you have to unsupercharge first (and not use it anymore)...
View attachment 06ramconfig.rar
you can push it with a file manager and reboot the phone. push it without archive ofc.
oh well... glad it solved out for ya

Free Xprivacy permission/privacy manager

"XPrivacy can prevent applications from leaking privacy sensitive data. XPrivacy can restrict the categories of data an application can access. This is done by feeding an application with no or fake data. There are several data categories which can be restricted, for example contacts or location. For example, if you restrict access to contacts for an application, this will result in sending an empty contact list to the application. Similarly, restricting an application's access to your location will result in a set location being sent to the application."
more info on the original xda thread, or github. The authors describe how it is better than other privacy solutions.
xposed installer is a framework for modules (such as xprivacy). This has the potential to allow tremendous customization of your ROM without having to flash a custom ROM.
{
"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"
}
Basic Info
1. requires xposed installer (which requires root access) before installing xprivacy (i.e. both files need to be installed)
2. files are designed for Android 4+, but there is a version that works with Gingerbread (android 2+)
3. will work on almost any android ROM. Works on my locked, stock, 2.3.4 sprint ROM.
How to install:
First step for everything you do: Create a nandroid backup and make sure you know how to restore it!
For the framework:
1. Download XposedInstaller.apk (for the corresponding version android ROM you have) and install it
2. Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
3. Reboot
4. Done!
For any modules you want to install:
1. Download <module>.apk and install it (get the version for your corresponding android ROM)
2. Launch the Xposed Installer and go to the "Modules" section
3. Enable the module by checking the checkbox (verification stage)
4. Reboot
5. Done!
credit: rovo89, M66B, liudongmiao, et al.
Requires root?
If you have a Sprint stock, locked rom, how were you able to load this program without root access?
armoredsedans said:
If you have a Sprint stock, locked rom, how were you able to load this program without root access?
Click to expand...
Click to collapse
The bootloader is locked, but the ROM is rooted (i.e. has superuser privelages).
There is a new xposed module (backported to gingerbread) that fixes an android "master key" security hole.
Its nice to be able to get security fixes like this since Sprint/Motorola no longer support this device.

[HELP] Install Viper4Android to ZTE nubia Z7 Max Stock LP

ViPER's Audio @ http://vipersaudio.com/blog/?page_id=11 said:
{
"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"
}
XDA Thread: http://forum.xda-developers.com/showthread.php?t=2191223
ViPER’s Audio is an audio enhancing software to provide everyone with better audio experiences in various platforms such as smartphones and PCs.
ViPER’s Audio is founded by Euphy Wong (known as ViPER520). ViPER’s Audio has been a popular audio mod in China. Co-founder Jasper Loo (known as zhuhang) extended its popularity globally through xda-developers forum. It has now gained fame and stand its ground in the audio mod field.
Click to expand...
Click to collapse
This is my personal walkthrough for Viper4Android (V4A) installation, after [THREAD="3108822"]upgrading a ZTE Nubia Z7 Max to the stock Lollipop ROM v3.09[/THREAD].
Most info here was scrapped from "[THREAD="2191223"][APP] Official ViPER4Android Audio Effects (FX v2.3.4.0) - Lollipop support and more![/THREAD]".
At first I just installed as usual (sideloaded) the V4A APK I got inside the ZIP downloaded (there are two versions, use the one with the name ending in "A4.x.apk", the other one is for old Androids; see quote above for links). Also as usual, when you open the App, it will ask permission for a driver installation (so ROOT is required for this) and to reboot, after which if you check the "Driver Status" from its 3-dot-menu, you'll get a square toast stating "Abnormal" and "Unsupported".
What you need to do to solve this is:
Make sure your device is rooted and has busibox installed;
(if you're unsure about any of this terms, research them first and come back only after you fully understand them)
Do a fresh install of 'ViPER4Android_FX_A4.x.apk' but don't run it;
Using a file manager App, locate V4A installation folder (probably '/data/app/com.vipercn.viper4android/') and move it to '/system/priv-app/';
Reboot;
V4A will now be installed as a system App, so just open it and agree to have its driver installed;
Reboot;
Open V4A again and check the "Driver Status" from its 3-dot-menu (it'll still say "Abnormal" and "Unsupported");
This is caused by SELinux security being enforced, if you don't care about it, you could just open a terminal App and type the following command to deactivate it (you'll need to do this after every reboot):
Code:
su
set enforce 0
If you want to preserve SELinux security, you'll have to copy the lines below to a script with the appropriate permissions (755) and place in '/system/etc/init.d/' to make it stick upon rebooting:
Code:
#!/system/bin/sh
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
Unfortunately, this won't be enough, because the stock Z7 Max doesn't execute Init scripts, but you can solve this with a free OSS App like [THREAD="2986129"]Kernel Adiutor[/THREAD], which will run your startup scripts after being set to emulate Init.d (look under the "hamburger" menu).
Lastly, and for good measure, edit your 'build.prop' file (above mentioned Kernel Adiutor can make a backup and edit, too) and change/add the following keys:
tunnel.decode=false
lpa.use-stagefright=false
lpa.releaselock=false
lpa.decode=false
EDIT: if you get Bluetooth problems or intermittent silences, try adding "ro.bluetooth.request.master=true" as well (appears to work, found here).
If you open V4A after doing 8. or 9., you should be rewarded by the "Driver Status" changing to "Normal" and "Supported".
Beware, though, that audio Apps will default to routing through the Dolby Digital Plus system audio processor unless you disable it (top right corner button).
V4A Normal Driver Status Display:

[ROM][Z3C/D5833/D5803][5.1.1][23.4.A.1.232] Make it easy to customize

Hi everyone. This is my first public ROM
The goal of the ROM is to keep itself as stable as the offical one while
making it lite-weighted and customizable for beginners.
The ROM is based on Sony's offical build D5833-23.4.A.1.232_CustomizedTW
and I move all replacable or useful applications to data/app so you can add or remove them in your favor
Features
Support Locked/Unlocked bootloaders
Remove totally useless system apps
Move replacable system apps to /data/app so you can uninstall them!!!
(/data/app are deodexed!!!)
Update all apps to the latest one
(Still Z3C's. I won't integrate other device's apps to ensure the stability)
Auto-rooted with SuperSU-ver2.46
Auto-install XZDualRecovery-ver2.8.21
Auto-install Xposed-ver75.sdk22
Auto-install busybox
init.d support
Enable sdcard media r/w permission to compatible with old apps
Enable adb debug mode by default
Performance and battery enhancement
A cute boot animation
Requirements
Sony Z3 Compact (No need to unlock the bootloader)
Recovery: I only test it with TWRP, but CM should also work
Steps
Put this ROM into you SD card
Reboot into recovery (I use TWRP)
For anyone who ever installed different Xposed before, it's suggested to
uninstall it by flashing the xposed-uninstaller-20150831-arm.zip
For Android 4.x users, please do factory reset and wipe data
For Android 5.x users, it's not needed but suggested to wipe data
Install this ROM
After installation, reboot to system, and enjoy the new world!!!!! :highfive:
Download link
PLEASE DO NOT MIRROR THE ROM OR REPOST WITHOUT MY AUTHORIZATION!!!
I already tested it on D5833 for a while.
But I cannot test it on D5803 since I don't have the device.
Nevertheless, it should work after comparing the ROM among others.
If there is any essential feature not work, just reply in this thread instead of PM. Thanks!!!
D5833/D5803: https://mega.nz/#!cYom1TKA!TG1_pp0Qx4hLqQvdZbAmCMzolVlmgR1rYbT_jncIDlc
Changelogs
20151103
Remove Lucky Patcher since it's banned here. Thanks Gandolf's remind.
20151101
Initial release
Screenshots
{
"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"
}
Thanks for your contribution :victory:
Chainfire for SuperSU
[NUT] for XZDualRecovery
rovo89 for Xposed framework
Jeff Mixon for build.prop analysis
Any screenshot please. Thank you.
acatoan said:
Any screenshot please. Thank you.
Click to expand...
Click to collapse
Added
I get an "error executing binary in zip" as soon as I start the flashing.
It changed my model to 5833 from 5803 and I can not find the gravity box menu..
It's OK now
why not base on .264?

[GUIDE] SafetyNet Fix for all AOSP based Custom Rom [Note8/S8+]

{
"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"
}
If you want to use Bank Apps (Like Google Pay, Paytm or Paypal) or Games (like pubg or cod) are Crashing
then this Forum will help you alot.
Follow the Steps Carefully
* I are not responsible for anything that may happen to your phone
* You do it at your own risk and take the responsibility upon yourself and you are not to blame me or XDA​
• For basicIntegrity
1) Open Magisk Manager
2) Go to the Settings
3) Enable Magisk Hide and Click on Hide Magisk Manager
4) Type Desired App Name and click on OK
5) Open Magisk Manager again
6) now basicIntegrity: true
• For ctsProfile
1) Open any Root File Manager
2) Now open/edit build.prop (all 3 files)
---- Location : [/system] , [/system/vendor] and [/system/vendor/odm/etc]
3) Replace all dreamlte to greatlte[for note 8]/dream2lte[for S8+]
---- eg: ro.system.build.fingerprint=samsung/greatltexx/dreamlte [replace with greatlte/dream2lte]
4) Save and Reboot the Device
5) Open Magisk Manager
6) now basicIntegrity: true & ctsProfile: true
Now if you want to use Bank Apps or fix Game crash then
1) Open Magisk Manager
2) Go to Magisk Hide and Select/Check the Bank App/Games
3) Make sure to Clear the Cache of the App.
RESERVED for future
There is a magisk module for this.
MagiskHide Props Config.
I don't know exactly but I guess the problem is about note 8 don't get android 10. So if we show our phone like note 9 (is get android 10) problem gone.
Before im try this, im using app and module like riru and hiden core module to fix SafetyNet. But after im install module riru and hiden core my Chrome App doesnt open.
After try this method, im pass the SafetyNet and my Chrome can be opened as normaly

Categories

Resources