I won't be working on this anymore cause there's no real point for me. Feel free to pick apart useful pieces or whatever
Injects init.d support: Via post-fs-data script if using magisk Via init script if system install (also installs setools by Xmikos (https://github.com/xmikos/setools-android)) Built with Unity installer by Zackptg5 (https://github.com/Zackptg5/Unity) and AnyKernel2 by Osm0sis (https://github.com/osm0sis/AnyKernel2/) More details in support thread.
- Update to Unity v4.4
- Update to Unity v4.3
- Switch to AK3 addon
- Update to Unity v4.2
- Update to Unity v4.1
- Bug fix with ramdisk patching
- Updated to Unity v4.0
- Update Unity from test branch for minapi of 17
- Unity v3.2 update
- Unity v3.1 update
- Unity v3.0 update
- Unity v2.2 update
- Updated to unity v2.1
- Unity v2.0 update
- Unity v1.8.2 update
- Unity v1.8.1 update
- Fixed limitation in zipname triggers - you can use spaces in the zipname now and trigger is case insensitive
- Removed setools - installs magiskpolicy instead
- Unity v1.7.2 update
- Unity v1.7.1 update
- Unity v1.7 update
- Unity v1.6.1 update
- Updated to unity v1.6
- Updated ak2
- Unity v1.5.5 update
- Redid ak2 logic - redo scripting (uses initd.sh rather than sysinit), has capability to run init.d scripts as post-fs-data (default) and late_start (add '-ls' to the end of the name of it), use this logic for all system installs
- Magisk uses magisk boot scripts but does the same thing
- Update it so it'll work with sysover if user chooses
- Unity v1.5.4 update
- Unity v1.5.3 update
- Unity v1.5.2 update
- Run all scripts except live boot as late start in magisk due to magisk mount occuring after post-fs-data script
- Initial rerelease
- Module GitHub