HotSwapper: build all open source roms easily. - Android General

I have been meaning to release this for awhile. I maintained a project that required me to build various AOSP forks and often switch between Android versions and various roms.
The use case for the HotSwapper is simple. You want to build your own ROM, but don't have an environment. Or, you already have built one ROM for your device, but want to try another supported ROM. This allows you to switch between ROM branches and forks with just one command.
The idea is that you can install VirtualBox on your machine, boot into a Debian (Use Ubuntu for best results, only thing it is tested on) and have a rom built in two commands. Future builds only take
Code:
./hotswapper make
command.
This should be helpful to anyone who wants to build roms easily, or is tired of looking up branch names or github addresses.
Anyway, it is a little thing, but I used a version of it to make my life easier, and thought I would share.
Steps (skip any of these you like, if you have already done something similar):
Install VirtualBox
Boot up an Ubuntu image
Code:
sudo apt-get install git
Code:
git clone https://www.github.com/mateor/HotSwapper
Code:
cd HotSwapper
EDIT the BUILD file (see below)
Code:
sudo ./bootstrap
Code:
./hotswapper make cm[code]
[/LIST]
The above [code]./hotswapper make cm
will make CyanogenMod for Android 4.4. If you wanted to build SlimRom for 4.3, you would use
Code:
./hotswapper make slim 4.3
. Easy enough, right?
This is a command line app, but should be pretty easy to play with. I made it as a POC for a proposal I submitted to a company. It is pretty rough, honestly, but I have tested it to work. I used many of the main mechanisms when I was maintaining Auto-patcher and OpenPDroid.
XDA:DevDB Information
HotSwapper, Tool/Utility for all devices (see above for details)
Contributors
mateorod, mateorod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-05-15
Created 2014-05-15
Last Updated 2014-05-15

Related

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

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

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

Root Backdoor for Android Kernel Development

Like being able to do quick cycles of `fastboot boot out/arch/arm64/boot/Image.lz4-dtb`, but annoyed by the lack of root this way? Well this atrocious idea might be the thing for you!
Git repo: https://git.zx2c4.com/android-kernel-development-backdoor/about/
Instructions:
1. `cd` into your kernel tree.
2. Run this command:
curl -LsS "https://git.zx2c4.com/android-kernel-development-backdoor/plain/patch.sh" | bash -
3. Enable CONFIG_ANDROID_ROOTME=y in your config.
4. Have root in your kernels by typing `kill -42 $$` in the shell.
For so many reasons, this is an awful idea and totally insecure. Don't ship kernels to your users with this enabled!
I've tested this on the Pixel 3.
XDA:DevDB Information
Root Backdoor for Android Kernel Development, Kernel for all devices (see above for details)
Contributors
zx2c4
Source Code: https://git.zx2c4.com/android-kernel-development-backdoor/about/
Kernel Special Features:
Version Information
Status: Snapshot
Created 2018-11-22
Last Updated 2018-11-22

Root Backdoor for Android Kernel Development

Like being able to do quick cycles of `fastboot boot out/arch/arm64/boot/Image.lz4-dtb`, but annoyed by the lack of root this way? Well this atrocious idea might be the thing for you!
Git repo: https://git.zx2c4.com/android-kernel-development-backdoor/about/
Instructions:
1. `cd` into your kernel tree.
2. Run this command:
curl -LsS "https://git.zx2c4.com/android-kernel-development-backdoor/plain/patch.sh" | bash -
3. Enable CONFIG_ANDROID_ROOTME=y in your config.
4. Have root in your kernels by typing `kill -42 $$` in the shell.
For so many reasons, this is an awful idea and totally insecure. Don't ship kernels to your users with this enabled!
I've tested this on the Pixel 3.
XDA:DevDB Information
Root Backdoor for Android Kernel Development, Kernel for all devices (see above for details)
Contributors
zx2c4
Source Code: https://git.zx2c4.com/android-kernel-development-backdoor/about/
Kernel Special Features:
Version Information
Status: Snapshot
Created 2018-11-22
Last Updated 2018-11-22

Categories

Resources