Seal Os Boot Animation Installer - Samsung Galaxy S7 Themes, Apps, and Mods

Seal Os Boot Animation Installer - Samsung Galaxy S7 Themes, Apps, and Mods

Seal Os Boot Animation Installer A zip flash file that installs Seal Os boot animation on the s7. Fully based on Dynamic Installer.
Compatible with roms that have the boot animation in the system/product/media or system/media folder.
LicenseThis program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
UninstallTo Uninstall go here.
Credits To@TOBY19k ( I Made this)
@BlassGO ( For making dynamic installer )
@Nikhil ( For helping me make addon.d script)
@Ivan_Meler ( For making Seal Os.mp4 with out it this wouldn't exist )
DownloadGitHub

Here's a preview

This is the news group. This is the support group.

Related

[ABANDONED][OUTDATED] Droid Universal Root (Root your Device without PC!)

Hi XDA Community!
"This is my first time to post a thread. Please consider me as a junior and don't be ignorant
This is all about rooting all almost devices without using a PC.
I called it...."
DROID Universal Root
or DROID U-ROOT
ROOT can access all features deep down into system, just like you are a Administrator in Windows Computer!
ROOT can give you more benefits like, optimize performance, save more battery life, completely remove unwanted user and system apps, and more!
That's why i created this small package
(ChainsDD has also his package but it's old : http://androidsu.com/superuser/)
REQUIREMENTS:
+ Android 2.3 Gingerbread to 4.2 Jelly Bean (Not yet sure for KitKat)
+ Android Devices with ARM Architecture, not yet available for x86, MIPS, etc.
+ An Android Device with a workable Recovery Mode Console.
(Custom and NON-OEM Recoveries are Recommended! More info...)
* With a SD Card at least 20MB remaining space, a system partition at least
12MB and a "/data" or internal memory with at least 10MB space remaining.
* Unlocked Bootloader (Bootloaders issued mostly in HTC, Motorola, etc. if Available)
NOTE : For users who are using DROID_U-ROOT_******--SIGNED.zip,
If installation fails, try these two packages.
DROID_U-ROOT_******_GB--SIGNED.zip contains Superuser files by @ChainsDD
while, DROID_U-ROOT_******_ICS+--SIGNED.zip contains SuperSU files by @Chainfire
(ICS+ Means its for Android 4.0 to 4.2)
COMING SOON:
* v 1.0.21 *
BIGGEST UPDATE EVER!
-- Fixed TYPO code in updater-script for GB Edition.
-- updater-script would be obsolete, we will now using the
binary source from @ClockWorkMod (coding)
to ensure rooting process!
-- More permissions fixes using scripts to ensure it's integrity!
-- Other architectures (x86, MIPS, etc.) would be available!
Version Changelog:
* v 1.0.1 *
-- Properly Signed all packages using APK-Multi-Tool (Hope it's more compatible!)
-- Dummy file contained in init.d directory in order to sign the whole package! (It will call "su" binary at boot)
* v 1.0.0 *
-- Initial Release
ALL OF INFORMATION MAY YOU WANT TO KNOW IS ALREADY
COMPILED IN A README FILE!!!
"All of files contained in DROID UNIVERSAL ROOT package are never modified any
file belongs/owned from the RESPECTIVE OWNERS. All of Copyright complaints and
infringements was unintentional."
More info in README!!!
Thank you.

README!!!
Code:
+===============================+
DROID UNIVERSAL ROOT
by JCCULTIMA
The Universal ROOT Package
for ANDROID!
+===============================+
TEXT-BASED README Version 1.2
[HIDE]
DISCLAIMER and COPYRIGHT POLICY
All of files contained in DROID UNIVERSAL ROOT package are never modified any
file belongs/owned from the RESPECTIVE OWNERS. All of Copyright complaints and
infringements was unintentional. Instead, please report it at XDA Forums
(@jccultima) to address all of these.
SU Apps and Binaries are owned and distributed by/from ChainsDD, Chainfire, etc.
and licensed under the APACHE Version 2.0
You may not use these FILES except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
APK's are repacked and published from Official Google Play Store.
Table of Contents
1. Information about ROOT
2. Advantages and Disadvantages of ROOT
3. What are the requirements to make it work?
4. How to install DROID UNIVERSAL ROOT?
5. Compatibility Notice
1. Information about ROOT
-------------------------------------------------------------------------------------
More info at: http://en.wikipedia.org/wiki/Android_Rooting
Android rooting is the process of allowing users of smartphones, tablets, and other
devices running the Android mobile operating system to attain privileged control
(known as "root access") within Android's sub-system.
Rooting is often performed with the goal of overcoming limitations that carriers and
hardware manufacturers put on some devices, resulting in the ability to alter or
replace system applications and settings, run specialized apps that require
administrator-level permissions, or perform other operations that are otherwise
inaccessible to a normal Android user. On Android, rooting can also facilitate the
complete removal and replacement of the device's operating system, usually with a
more recent release of its current operating system.
As Android derives from the Linux kernel, rooting an Android device gives similar
access administrative permissions as on Linux or any other Unix-like operating
system such as FreeBSD or OS X.
Root access is sometimes compared to jailbreaking devices running the
Apple iOS operating system. However, these are different concepts.
Jailbreaking describes the bypass of several types of Apple prohibitions
for the end user: modifying the operating system (enforced by a "locked bootloader"),
installing non-officially approved apps via sideloading,
and granting the user elevated administration-level privileges.
Only a minority of Android devices lock their bootloaders?nd many vendors such
as HTC, Sony, Asus and Google explicitly provide the ability to unlock devices,
and even replace the operating system entirely.
Similarly, the ability to sideload apps is typically permissible on Android devices
without root permissions. Thus, it is primarily the third aspect of iOS jailbreaking
relating to giving users superuser administrative privileges that most directly
correlates to Android rooting.
2. Advantages and Disadvantages of ROOT
-------------------------------------------------------------------------------------
An Android Device with a ROOT Access can give more functionality, such as by
Optimizing Performance both Software (Kernel, ROM) and Hardware (CPU, RAM, SoC)
Longing Battery Life, Uninstalling unwanted system apps, Forcibly transfer the app
to the SD Card (Even it's not supported) etc. All of these functions can separately
install using apps with a special SU (Root binary) system call.
Many users says that ROOT Access was a great function for a Android device.
But ROOT can cause vulnerabilities on your device and it's potentially dangerous
just because it can access deep down into a Android Sub-System such as modifying
system files, depending of which particular files or binaries would modify it by
users.
3. What are the requirements to make it work?
-------------------------------------------------------------------------------------
In order to make it workable smoothly, you/users must comply these requirements;
* Android 2.3 Gingerbread to 4.2 Jelly Bean (Not yet sure for KitKat)
* An Android Device with a workable Recovery Mode Console.
Custom and NON-OEM Recoveries are Recommended!
(More info: http://www.androidcentral.com/what-recovery-android-z)
* With a SD Card at least 20MB remaining space, a system partition at least
12MB and a "/data" or internal memory with at least 10MB space remaining.
This package will install a Superuser/SuperSU app in system/app/ directory, then
the su binary will install in a system/xbin/ directory. While the other functions
will be informed how at XDA forum.
4. How to install DROID UNIVERSAL ROOT?
-------------------------------------------------------------------------------------
BEFORE INSTALLATION...
Reboot your device to recovery mode, booting IT can be in different ways.
Case #1: Turning off the device and wait in a seconds to shut, and pressing
BOTH Power, Volume Up and Home Hard Buttons. This case are applicable
in many Samsung or other devices which it has a center button (HOME).
Case #2: Turning off the device and wait in a seconds to shut, and pressing
BOTH Power, and Volume Up Buttons. This case are mostly applicable
to the devices without a center button. (Soft Touch)
In some recoveries, some of them doesn't have a "select zip from sdcard" option.
So make sure you must rename the package to update.zip
INSTALLATION...
After that, Use the volume button to move, and home/menu/power button to select.
Some devices can select by tapping. Choose "select zip from sdcard" or
"select update.zip from sdcard". It will run if you rename this package
to update.zip!
AFTER INSTALLATION...
Reboot your device, wait for a moment to boot, and open your launcher menu.
When the Superuser/SuperSU app appeared, it means that you are ROOTED.
5. Compatibility Notice
-------------------------------------------------------------------------------------
NOT ALL ANDROID DEVICES are 100% workable in this package.
Many devices may not be easy to install cause of security features
such as OEM Recoveries build and provided by own manufacturers,
and locked bootloaders which it has a ability to restrict sideloading files
except their Official OTA Updates. It should be unlocked right away before
this procedure.
For users experienced Error 0 by installing this package, simply replace the
update-binary file from any of your stable update-binary.
Open the package using WinRAR then...
* META-INF/
* com/
* google/
* android/
! update-binary <<< Should be like this
* updater-script
* CERT.RSA
* CERT.SF
* MANIFEST.MF
To avoid device crashes, please make a backup through ADB (Android 4.0+ only) or
Custom Recovery (e.g. CWM). The developer is not responsible for Device Crashes,
Bootloops and other relative damages on your device.
README Version Changelog
1.0 Initial Release
1.2 Finishing and Adding more information
Don't Forget to Report us at XDA (Link Coming Soon...)
[/HIDE]

Idk what this is. OP says Stable and beta. I downloaded your signed beta rc 1.0 and it is nothing but supersu apk, su binaries, and busy box. The updater script seemed weird as supersu does all of the work in the updater-binary. Anyway, I have no idea what this is supposed to be. You might want to ask @Chainfire before repackaging his stuff though. It doesn't appear in your OP that you give him credit.
Sent from my AOSP on HammerHead using Tapatalk

[ZIP] LazyFlasher - the swiss army knife of flashing custom kernels!

LazyFlasher & no-verity-opt-encrypt
INTRODUCTION
Hello Users and Developers of XDA!
LazyFlasher is a custom kernel flashing tool designed to make it easy to dynamically modify ramdisks and inject kernel binaries into the current boot image.
It's the swiss army knife of kernel flashing for use in Team Win Recovery Project.
The intent behind it was to allow a 1 custom kernel fits all approach, where your users can flash single zip on any ROM for a particular device,
allowing your kernel to be compatible with the vast majority of custom ROMs already out there. It takes away the pain of building custom boot.img
for each and every variant a user requests and puts it into 1 low maintenance intelligent universal flashable zip.
You might already know of @osm0sis's AnyKernel2 project. This approach is similar to that. Back in late 2015 I decided to design a more compatible, more friendly, and more feature filled version. Since then, AnyKernel2 has apparently improved a lot so if LazyFlasher doesn't accomplish what you need, AnyKernel2 probably will.
LazyFlasher does not currently support ELF boot images.
For users of no-verity-opt-encrypt: This thread can also be used to discuss the no-verity-opt-encrypt project which is just a minimal version of the LazyFlasher framework.
Disqus thread: https://www.xda-developers.com/xda-...-is-an-alternative-to-the-anykernel2-project/
THE GITHUB REPOSITORY
You can find LazyFlasher's development and download it here: https://github.com/jcadduono/lazyflasher
LazyFlasher source code is distributed under the BSD 2-clause license. You can do anything you want with it, however, some of the binaries used by it are under GPLv2 or GPLv3 licenses.
FEATURES
ChromeOS support (ChromeOS test-key signing and recognition)
MediaTek device support (MTK headers)
SELinux policy injection support via sepolicy-inject
Example scripts to disable dm-verity or forced encryption during the install process (010-no-force-encrypt, 015-no-dm-verity)
A process that executes a sorted list of scripts for making the desired modifications (separate from the framework)
Handily unpacks, decompresses, applies changes, compresses, and repacks boot images quickly and safely
Supports Gzip, LZ4, Bzip2, and LZO ramdisks. Support for LZMA and XZ is a work in progress
Supports arm (armv7), arm64 (aarch64), x86 (i386), x86_64 (amd64), mips, and mips64 architectures
Supports dtb.img replacement (place it in the root folder named "dtb.img")
Scans fstab and partition locations for the boot partition, optionally allows a preset location
Intelligently installs kernel modules by copying the previous layout of /system/lib/modules and creating symlinks
Creates modprobe supported /lib/modules aliases if kernel modules are included in the installer (030-kernel-modules)
Installs new files to the ramdisk and sets their permissions automatically based on file type from ramdisk-patch (020-patch-ramdisk)
Includes an optional bbe tool for applying binary patches
Unnecessary architectures and tools can be removed to save space
Many useful functions and variables included in the patch.d environment to simplify modification/patching scripts (patch.d-env)
Simple "make" build system
SETTING UP LAZYFLASHER
LazyFlasher is only designed for building on Unix based systems such as Linux, Mac OS X, and FreeBSD.
To download it (feel free to fork it so you can have a copy on your GitHub to modify instead!):
Code:
cd ~/build
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git
cd lazyflasher
To use LazyFlasher, you'll probably want to take a look at the Makefile, config.sh, and META-INF/com/google/android/update-binary (a shell script).
There's a few things you can change there to personalize it to your needs.
(make another git commit to save your setup!)
You should also check out the README! There is a lot of useful information there.
Once the installer is set up to your liking, all you have to do to build it is copy the resulting kernel binary from your kernel build output into the lazyflasher folder.
If you have built with kernel modules (make modules_install), copy build/lib/modules -> lazyflasher/modules.
Now simply run:
Code:
make
A TWRP flashable zip and sha1sum is created!
You should consider signing the zip with AOSP test-keys so that users can verify its integrity before flashing it.
LOOKING TO TRIM DOWN THE INSTALLER?
I have forked the kernel-flasher branch to a branch called kernel-flasher-arm64-minimal. This provides all the features of kernel-flasher except sepolicy injection and bbe, and only supports arm64 devices. It reduces the minimum zip size from 1860 KB to 200 KB.
You can use this branch instead if you like. If you're using another architecture, just look at the trimming commit as an example and apply it for your arch.
BUT I AM ON LE WINDOWS!
How did you build your kernel binary?!
Anyways, there is an alternative for building it on Windows.
You can download the LazyFlasher kernel-flasher branch as a zip file from GitHub and extract it somewhere on your PC.
Make your modifications using Notepad++.
You can then use a tool such as 7-zip to create a zip file by selecting everything in the folder, right clicking, and going to 7-Zip -> Add to "lazyflasher.zip".
LIMITATIONS AND KNOWN ISSUES
It will not run on TWRP built in Android 4.3 or earlier (usually builds older than 2.8.0.0)
Requires Busybox to exist in the TWRP build. All official builds should have this.
There may occasionally be some devices that are unsupported due to extreme modifications made to the boot image format by the manufacturer. If you have one of these devices, feel free to contact me and I will try to add support for it if it is worth the effort.
If you have an issue, please gather a recovery.log from TWRP after flashing and I will try to look into it. I can't do anything to diagnose your problem without a recovery log.
Code:
adb pull /tmp/recovery.log
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel image or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
WHO ELSE IS USING LAZYFLASHER?
I'll keep a list here of cool projects that are using it. Feel free to ask for yours to be added.
The Kali Linux NetHunter project (GitHub, Website)
no-verity-opt-encrypt, no-verity-force-encrypt, twrp-data-fstype-swap (Website/Download)
WHAT IS LAZYFLASHER USING?
LazyFlasher makes use of a few open-source projects. You can find their source code here:
bootimg / libbootimg for boot image unpacking/repacking - https://github.com/jcadduono/android_external_libbootimg
bbe for binary patching - https://github.com/jcadduono/android_external_bbe
bzip2 for ramdisks - https://github.com/jcadduono/android_external_bzip2
lz4 for ramdisks - https://github.com/jcadduono/android_external_lz4
futility for ChromeOS boot image signing - https://github.com/jcadduono/platform_external_vboot_reference
sepolicy-inject for sepolicy policy injection - https://github.com/jcadduono/android_external_sepolicy-inject
XDA:DevDB Information
LazyFlasher, Tool/Utility for the Android General
Contributors
jcadduono
Source Code: https://github.com/jcadduono/lazyflasher
Version Information
Status: Stable
Current Stable Version: 5.1
Stable Release Date: 2017-02-01
Created 2017-02-02
Last Updated 2017-02-07

We should give this man award.
The Job that he has done with this and Nethunter is just amazing.
Thank you and keep up the good work

Nice tool. Keep up a good work

Great Work! Hope i can include it into my Projects in the Future...
Thanks a lot for that!

You are a goddamn god.

Honestly Annoying said:
You are a goddamn god.
Click to expand...
Click to collapse
thx dude, usually that phrase is reserved for Chainfire accomplishments

y u nu support mah Indian AF MTK fone @jcadduono
Kidding, awesome work on this though!

Good one , this man develops for the developers !

Is it possible to have this on i9100 ? AnyKernel2 doesn't work with i9100

Skyline said:
Is it possible to have this on i9100 ? AnyKernel2 doesn't work with i9100
Click to expand...
Click to collapse
nope, no plans to support that device, surprised they are still out there, i would expect most to be dead emmc by now. :|
you can probably modify boot-patcher.sh to copy partitions to split-img folder then flash them back instead of using bootimg
i don't even know if lazyflasher's binaries will run on any of the i9100 twrp builds. might be too old.
if i can get an example layout of i9100's partitions i can fork it to a new branch, called kernel-flasher-sgs2 and make it compatible for you guys.

jcadduono said:
nope, no plans to support that device, surprised they are still out there, i would expect most to be dead emmc by now. :|
you can probably modify boot-patcher.sh to copy partitions to split-img folder then flash them back instead of using bootimg
i don't even know if lazyflasher's binaries will run on any of the i9100 twrp builds. might be too old.
if i can get an example layout of i9100's partitions i can fork it to a new branch, called kernel-flasher-sgs2 and make it compatible for you guys.
Click to expand...
Click to collapse
They are too old but still supported by lineage 14.1 and official twrp 3.0.2-1 without any problems
osmOsis dev of anykernel2 said that i9100 and older devices are having different boot img header format when i tried to run anykernel2 script it says Android magic is not found something like that

interesting tnx

Wow...
I'm just recognizing now, how powerful lazyflasher is ...
Setting default.prop values and settings. Disable Encryptions and so on. Wish I could contribute something but I'm still learning how it works. For now I've just included lazyflasher into my PATCH to disable DM Verity and forced Encryption and to make some edits on the default.prop. That's really useful since the build.prop doesn't allows such deep changes.
@jcadduono what would be in the Theory possible with the Lazyflasher? Could we add things like Gouverneurs or default Kernel Clockings? Init.d Support? Sorry if I sound noobish :angel:

So, uh, is there a TL;DR for lazy people? :silly: :laugh:

@jcadduono this is absolutely awesome. thank you for your hard work.

Hope that someone can dev nethunter to Asus zenfone 5 t00f :fingers-crossed:

can you please make a tutorial vedio of it because i don't get it and i'm sorry for my stupidity

Will it work for Android Oreo / LOS 15?

Did anyone succeeded in removing dm-verity? I got this error

good

[Script] [Universal] [F-Zip] Recovery Flashable Zip generator for Linux & android

This thread will not be maintained anymore. The source code will be still available and updated. So, anyone interested can still download and use this script from here.
F-zip: Universal recovery flashable zip generator for Linux & android
/* What is F-zip about? */
"F-zip is a universal shell script designed to make recovery flashable zip files with a few simple steps“
/* For those it is helpful? */
Anyone (devs/newbies) who has something (boot.img/apps/libs) to flash and do not want to do all the work to make a recovery zip manually.
/* Background */
After encountered several errors while flashing manually made recovery zips, I made several scripts for my personal use. Now I decided to combine all and share as a universal script for generating recovery flashable zip for various purposes including
Flashing “boot.img”. (Caution: This feature is by default optimized for Samsung Galaxy S5 (kltexxx). Proper modification in the “fzip.sh” (line# 30) will be required for other devices. Don’t worry, you can easily find such details from any other working ROM/Kernel zip).
Flashing app(s) to “/system/app” & “/system/priv-app” (up to a maximum of 5 folders is presently supported though it is infinite without separate folder(s). That is directly as “.apk”).
Flashing "framework-res.apk", into “/system/framework/”
Flashing "bootanimation.zip" (only for aosp ROMs) to the "/system/media".
Flashing infinite number of library (typically “.so”) files into “/system/lib”.
Flashing infinite number of frameworks (typically “.jar”) files into “/system/framework”.
/* Where it works? */
It will works on any Linux and Linux based operating systems including android. The Linux system might be native or with in a virtual box or even the bash inside Windows 10.
/* DISCLAIMER!! */
Code:
I am not responsible for any damage to your device. Everything you are doing on your device is on your own risk.
You have all the chances to mess up your apps (and very rarely the entire ROM), in case if you did some stupid mistakes on this script. Use this script on your own risk.
Please note that flashing anything will mostly void your warranty.
/* How-to-use? */
1. clone or download f-zip repo into your Linux PC or Android device.
2. copy "boot.img", if any, into the root folder. Caution: Don’t forget to modify “fzip.sh” (line# 30), if your device is anything other than Samsung Galaxy S5 (kltexxx).
3. copy the app folder(s) in to "/system/priv-app/" or/and "system/app/". You may also copy the “.apk” file(s) directly to “/system/app/” or/and “/system/priv-app/” (without folder) if your app/ROM supports to do so.
4. copy library (typically “.so”) file(s), if any, into “/system/lib/”
5. copy modules (typically “.ko”) file(s), if any, into “/system/lib/modules/”
6. copy framework (typically “.jar”) file(s), if any, into “/system/framework/”
7. copy "framework-res.apk", if any, into “/system/framework/”
8. copy "bootanimation.zip" (only for aosp ROMs) file, if any, into “/system/media/”
9. modify fzip.sh accordingly (please see instructions below)
10. open terminal and cd to the root folder of f-zip
11. run ". fzip.sh" (in Linux) or “sh fzip.sh” (in android).
12. The recovery flashable zip file will be generated in the root folder.How-to-modify shell script?
More information can be found here.
/* Video Tutorial (Android mobile) */
A video demonstrating the use of this script in an Android mobile is available in this YouTube link.
/* F.A.Q */
Qn. Will this script works on windows native cmd?
Ans. No.
Qn. Is this script will work on the Bash inside Windows 10?
Ans. Yes. It will work on all the Linux and linux based (either native or virtual) environments.
Qn. I’m a Windows fanboy. I don’t have any working Linux environment at all, and too lazy to do these things in my android device. Is it still possible to use this script?
Ans. Yes. You can use your windows to add the necessory files/folders and also for editing “fzip.sh” (always use “gedit” or “Notepad++” for editing “fzip.sh”). Once you done, simply copy the folder into your android device and follow the remaining instructions.
Qn. Is it possible to make a flashable “boot.img” to “XXX” device using this script?
Ans. Yes. However, proper modification in the "fzip.sh" (line# 30) is required.
Qn. Can you make a similar script for Windows?
Ans. No. I don’t have enough knowledge to do that. Sorry.
XDA:DevDB Information
F-Zip, Tool/Utility for all devices (see above for details)
Contributors
sunilpaulmathew
Source Code: https://github.com/SmartPack/
Version Information
Status: Beta
Beta Release Date: 2017-09-08
Created 2017-06-14
Last Updated 2017-09-08

Chang-logs
This thread will not be maintained anymore. The source code will be still available and updated. So, anyone interested can still download and use this script from here.
3. November 08, 2017
Version 1.3.0.
Added support to flash modules. Some scripts are added to hide the unused folders from output zip. The entire script is now much more simpler.
3. September 23, 2017
Version 1.2.0.
Added support to Framework-res.apk. The entire script is largely simplified in order to make the flashing of "boot.img", "bootanimation.zip", "framework-res.apk", ".jar" & ".so" much easier.
2. June 23, 2017
Version 1.1.0.
Added supported to flash "bootanimation.zip" (only works on ROMs hat supports that functionality) and framework (typically ".jar") files.
1. June 15, 2017
Initial release
Version 1.0.0.

Reserved

Docker TWRP CICD

TWRP CICD Project
This is my personal effort given to you, the community, which spends a lot of hours to craft a fully-functional and perfectly tuned ROM for our beloved Smartphones!
What is it?
This project aims to provide a Build system for Android Developers which will be able to build a TWRP recovery image for a different set of Codenames given, automatically for you, ( by default ) every night. Not only built stock sources that are already available on TWRP Github account, but feel free to build even your custom code thanks to the support of local_manifests/*.xml fully supported by this Docker.
Where can I find it
CICD
- Github: https://github.com/julianxhokaxhiu/docker-twrp-cicd
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/docker-twrp-cicd
Why?
At the current status I find very time consuming the task to always setup the environment the right way to build a sporadic recovery for any kind of device, depending on the tree.
Therefore this projects aims on providing an easy-to-use build system which may help you on providing a Ready-To-Flash IMG at the end of each Build round. The same you would download from twrp.me website.
How does it work?
This is a pre-packaged Docker system based on Debian, with all the dependencies in place to correctly build ( even in an optimized way ) any TWRP codename image. A cronjob will take care to start the build script on the configured time ( by default 10:00 UTC ~= 02:00 PDT ), which then will take care to build every codename given with an environment variable to the Docker.
All you need from now on is just the Docker Engine installed on your favourite Linux distribution.
I want to use it right now!
I am pretty sure you want! The Docker has now been tested for a nearly a Month and I'm successfully installing my own builds for a couple of weeks on different devices ( really a great satisfaction! ).
If you want to run it as well, I suggest you to take a look at this Bash script that will run for you the Docker. Since the script has been studied to work on top of the "VPS Powered By Docker" project, I suggest you to take a look at it. Although nothing is preventing you to use it in your favourite way.
Requirements
See the detailed list on the project README.
What about License
All my projects are always developed with MIT license, which means feel free to do what you want with it. I don't really care if you do business with it, it was a great challenge for me reaching this autonomous entity to run, therefore I don't mind of possible outcomes of it. Although Issues are always welcome for improvements, if any found, of suggestion for a possible feature enhancements.
Enjoy!
XDA:DevDB Information
TWRP CICD, Tool/Utility for all devices (see above for details)
Contributors
JulianXhokaxhiu
Source Code: https://github.com/julianxhokaxhiu/docker-twrp-cicd
Version Information
Status: Testing
Created 2018-01-01
Last Updated 2018-01-01

Database Info

welcome