Database Info

[MTD][TW][DEV][INIT.D]Base boot.cpio.gz for TW on MTD

I have been trying out the various TW roms that run on MTD and have noticed some problems with the init.rc files that are being used, so I decided to create something that could be used as a base by others. I'm not sure who created the first TW rom on MTD, but they all seem to have mostly the same init.rc file, so I started from the one in tortel's EI22-Stock-ish MTD.
Things I changed:
Various changes and additions from the CM7 version
Removed plus tweaks (all of this can be taken care of elsewhere)
Added init.d support
Added support for /etc/init.local.rc
For init.d support to work, your rom must have the file /system/bin/sysinit, containing something like so:
Code:
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d
Every rom I've seen so far has, so it shouldn't be a problem.
How to use:
If you're not familiar with the format of the boot.img file that is flashed to the boot partition, check my other thread here. Basically is contains the zImage, and two ramdisks: boot and recovery. The zImage contains the kernel and a ramdisk: initramfs. The init.rc is located in the boot ramdisk, so I will distribute a copy of that. You can put this into your rom or kernel by deconstructing your boot.img with extract_boot.sh, replacing the boot.cpio.gz with this, then rebuilding the boot.img with mkshbootimg.py
Download:
boot.cpio.gz - 1.2 MB

Thank you. What I need is what changes the the kernel are needed to make a kernel work with MTD. I tried comparing my source tree with Tortell's but he had so many tweaks that it was hard to know what was really needed to make it work.

I thank you greatly for this good sir, and for all of your help !

[KERNEL]PowerSaving kernel with vocpcm support at github

As you may know farmatito's powersaving kernel is really saving power:
http://forum.xda-developers.com/showthread.php?t=1010932
However, his patches are hard to apply, so I setup a github repo with all patches applied:
github.com/bood/htc-magic-kernel
(not having enouth posts to post a outage url link yet...)
I also ported the vocpcm module so you can run rVoix on it
I only tested on my HTC TIM (32A) phone with old radios
Also, my original camera app does not work with this new kernel (I flashed the new kernel only, apps are untouched), appreciate that if anyone know how to flash it.
Instruction to flash the compiled kernel (32A only)
1. Do a backup
2. enter fastboot
3. unpack the attached 7z file
4. fastboot flash zimage bood-2.6.35.14-autogroup-vocpcm-kernel
5. reboot to recovery
6. adb shell mount -a
7. adb push wlan.ko-bood-2.6.35.14-autogroup-vocpcm /system/lib/modules
8. reboot normally
Update Logs:
2012/02/03
Updated a compiled kernel (autogroup version for 32A) with wlan.ko
2012/02/02
1. Applied all patches except BFS patches since I don't use it
2. Ported vocpcm module

Hello, thanks for that! Would gladly try the compiled version if possible, since I'm using Linux. Thanks in advance.

Actually it is compiled in Linux.
Anyway I've uploaded a compiled version, give it a try!
Sorry didn't made a flashable zip, since the ramdisk could be different.
saibot64 said:
Hello, thanks for that! Would gladly try the compiled version if possible, since I'm using Linux. Thanks in advance.
Click to expand...
Click to collapse

HEh, what I meant was 'I don't use Linux' Thanks for that, will try it !

[Q] Kernel Compiling

Hello guys,
i have compiled a kernel for the oneplus one. But i am not sure if it will work so i want to know if these steps are right.
At first i forked francos kernel source + ramdisk.
After that i went into kernel source directory and typed this into the termnial.
Check my make.sh script https://github.com/DerRomtester/one_plus_one/blob/cm-11.0/make.sh
After that i went into the ramdisk source and extracted francos boot.img and deleted a file like this boot.img - zImage
Than i went into the kernel directory and started the build.sh file to get an boot.img file.
Everything went fine.
I had no errors. Are these steps correct.
My kernel source: https://github.com/DerRomtester/one_plus_one
Ramdisk source: https://github.com/DerRomtester/ramdisk_one_plus_one
I hope some devs can help me.

[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

[MODS][SCRIPTS] Zackptg5's Misc Projects

Many of you already know that I have them all of my projects listed with their respective xda threads and download links on my website, but not all of them had an xda thread. So rather than cluttering xda with a new thread for each individual mod I make, I decided to put the smaller ones here :victory:
Binaries
Cross Compiled Binaries For Android Build Script
The new home for my binary build script. Combines what was formerly GNU and Misc build scripts into one. It contains a good number of useful binaries such as aria2, bash, coreutils (with advanced cp/mv - adds progress bar functionality), curl, gawk (GNU awk), sed, vim, zsh, and more. Check it out to see the expanding list
Keycheck
Finally tracked down the source code for this. This will compile the keycheck binary so you can use vol key selections and what not. Uses a modified build script by @osms0sis. Instructions on the repo
Zip for Android
This builds the zip binary, prepared for android by cloudchou @github in addition to a build script by @osm0sis that I modified for this. Just clone the repo, cd to jni, chmod the build script, and run it
Mods
Cross Compiled Binaries For Android
This zip contains a term script which can install any number of the growing list of binaries I've managed to cross compile for android. Here's the repo where they're all stored
Codec Power Gating Disabler [Deprecated]
Another straightforward one. Disables codec power gating. It's needed for some audio mods like @chdloc's Biquads
Kernel Sepolicy Patcher [Deprecated]
Unlike most sepolicy mods out there, this one changes sepolicy at the kernel level - meaning no boot script crap so it'll work regardless of other mods/root solutions (or lack there of). You can choose between enforcing or permissive while flashing it - you can use this to switch at will to test stuff out or whatever
Module Manager [Deprecated - not needed with magisk v24]
Magisk Canary v23.x got rid of the magisk-modules-repo from the app. This term script replaces that temporarily until an in-app solution is implemented. Allows you to update and install mods with ease.
Overlay Mount Fix [Deprecated]
Fix for overlay mount related issues with magisk - often seen in oneplus devices with /product
Misc
Searx Instance
Searx is a metasearch engine with a focus on privacy. It allows you to search many search engines at once without being tracked by them - I use it to remain private while using google and to for scientific journal article searching (science tab). I have more details on what it is/setup here on my website
More will be added when I come out with them. For a complete list of all of the stuff I work on, check out my website linked at the top of this post
Audio Mod Troubleshooting Guide
XDA:DevDB Information
Zackptg5's Misc Projects, Tool/Utility for all devices (see above for details)
Contributors
Zackptg5

Earlier this week I got Android Auto in my car. I never considered that Viper4Android wouldn't work with it. I was hoping the USB Policy Patcher would fix that but it didn't. It looks like this is a problem for most, if not all people.
Has anyone found a way to use V4A while connected to Android Auto through a USB cable? If so, please explain what you had to do. Thanks.

Updated mods for new unity 2.2
Also added option to notification_helper remover to remove libvolumelistener.so

@Zackptg5
If i want to use your Bash for android in a kitkat stockrom.. then the following zip is fine?..
I extracted the main files from your zip and made a simple zip...
since in Magisk Manager ..description about your bash for android says it needs 5.0+.....
Thanks

HemanthJabalpuri said:
@Zackptg5
If i want to use your Bash for android in a kitkat stockrom.. then the following zip is fine?..
I extracted the main files from your zip and made a simple zip...
since in Magisk Manager ..description about your bash for android says it needs 5.0+.....
Thanks
Click to expand...
Click to collapse
The compiled zip is for lollipop+. If you want it for older, go to the bash build script link in the OP and compile arm binary for Api 19 (or older)

Zackptg5 said:
The compiled zip is for lollipop+. If you want it for older, go to the bash build script link in the OP and compile arm binary for Api 19 (or older)
Click to expand...
Click to collapse
Thanks for quick reply...
But I dont have a pc sir...

HemanthJabalpuri said:
Thanks for quick reply...
But I dont have a pc sir...
Click to expand...
Click to collapse
Build script is for Linux. I'll try building later today

HemanthJabalpuri said:
Thanks for quick reply...
But I dont have a pc sir...
Click to expand...
Click to collapse
Here you go, latest bash stable compiled for kitkat (API=19) (and newer) arm devices

Zackptg5 said:
Here you go, latest bash stable compiled for kitkat (API=19) (and newer) arm devices
Click to expand...
Click to collapse
Thanks a lot for your time..
and Happy New Year...
but I just place in xbin without any other files?
i.e., /system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?

HemanthJabalpuri said:
Thanks a lot for your time..
and Happy New Year...
but I just place in xbin without any other files?
Click to expand...
Click to collapse
Right. Then chmod 0755 it

Zackptg5 said:
Right. Then chmod 0755 it
Click to expand...
Click to collapse
/system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?
I saw these files in your main zip v1.8.4

HemanthJabalpuri said:
/system/etc/bash/bashrc
/system/etc/bash.bash_logout
/system/etc/bash.bashrc
are not needed?
Click to expand...
Click to collapse
They're technically not needed but can be useful. You can place them manually, or unzip the bash module zip and replace the bash binary in the arm folder in the custom.tar.xz folder with the one I attached

Added zip and zipalign binary build repos

Updated bash to v5.0 stable

Zackptg5 said:
Updated bash to v5.0 stable
Click to expand...
Click to collapse
API 19?
also why nanodroid bash is 4.*mb and yours is 1.*mb?

HemanthJabalpuri said:
API 19?
also why nanodroid bash is 4.*mb and yours is 1.*mb?
Click to expand...
Click to collapse
I have it as minimum of 21 because that's the magisk minapi so I'm just keeping it consistent. You can always compile it for 19 with my build script here: https://github.com/Zackptg5/Bash-for-Android-Build-Script
My compiled binaries are stripped which means that inessential stuff (things not required for normal functions) were removed. See more on that here: https://en.wikipedia.org/wiki/Strip_(Unix)

the Kernel Sepolicy Patcher dont work for j5 pro android 8.1 twrp says error 1 when try to install

tutibreaker said:
the Kernel Sepolicy Patcher dont work for j5 pro android 8.1 twrp says error 1 when try to install
Click to expand...
Click to collapse
Log?

That all the rom installed busybox, and i try 2 versions of it and Same results

tutibreaker said:
That all the rom installed busybox, and i try 2 versions of it and Same results
Click to expand...
Click to collapse
Can you save the actual recovery log so I can see the cause of the error? After flashing zip, go to advanced -> copy log