Related
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
wizzROM a12 Creator
for Samsung a125
Turn any stock or custom OneUI into a QwizzROM or RwizzROM
Also see the Magisk module in post#2
OneUI 2.0 will become QwizzROM
OneUI 3.1 will become RwizzROM
Debloated ROM with Extras
Extras:
Battery charge limit
Clean Master
ES file explorer
HKtweaks
SimpleReboot
Root Explorer
Zarchiver
Make sure your OneUI ROM iis running befote you start
Installation
1 Backup system from recovery
2 Install the creator
3 Reboot
4 Enjoy
For better performance add my kernel
physwizz a12 kernel version 2 & 3
physwizz a12 kernel version 2 for u1 Based on a125f For OneUI 3.1 (May be unstable for some GSIs) V3 for u2 in post#2 Samsung restrictions disabled More CPU governors Optimised for performance Install from TWRP. Ignore the error message during...
forum.xda-developers.com
Name your wizzROM (optional)
1. Use a root explorer to copy and paste system/build.prop to new location
2. Edit build.prop like this
ro.build.display.id=<your-name>
3. Use zarchiver to paste the new build.prop into the system folder inside wizzROM-creator-a12.zip
4. Install wizzROM-creator-a12.zip
@physwizz
wizzROM Creator module for Magisk
for all Samsung a-series phones
Turn any stock or custom OneUI into a QwizzROM or RwizzROM
OneUI 2.0 will become QwizzROM
OneUI 3.1 will become RwizzROM
Debloated ROM with Extras
Extras:
Battery charge limit
Clean Master
ES file explorer
HKtweaks
SimpleReboot
Root Explorer
Zarchiver
Make sure your OneUI ROM iis running befote you start
Installation
1 Backup system from recovery
2 Install the creator from Magisk
3 Reboot
4 Enjoy
Name your wizzROM (optional)
1. Use a root explorer to copy and paste system/build.prop to new location
2. Edit build.prop like this
ro.build.display.id=<your-name>
3. Use zarchiver to paste the new build.prop into the system folder inside wizzROM-creator.zip
4. Install wizzROM-creator.zip
@physwizz
Thanks for your work!
T
LAST_krypton said:
Thanks for your work!
Click to expand...
Click to collapse
Thanks.
I'm thinking of buying a12 since I dropped my a20 and cracked the screen.
Development is a bit tricky with mediatek.
Most of my kernels are Exynos.
Although I have built for a10s which is mediatek
physwizz said:
T
Thanks.
I'm thinking of buying a12 since I dropped my a20 and cracked the screen.
Development is a bit tricky with mediatek.
Most of my kernels are Exynos.
Although I have built for a10s which is mediatek
Click to expand...
Click to collapse
A custom kernel would be nice for this phone.
LAST_krypton said:
A custom kernel would be nice for this phone
Click to expand...
Click to collapse
This one works
physwizz a12 kernel version 2 & 3
physwizz a12 kernel version 2 for u1 Based on a125f For OneUI 3.1 (May be unstable for some GSIs) V3 for u2 in post#2 Samsung restrictions disabled More CPU governors Optimised for performance Install from TWRP. Ignore the error message during...
forum.xda-developers.com
My understanding is that you have to be rooted to install this?
mzahs said:
My understanding is that you have to be rooted to install this?
Click to expand...
Click to collapse
Yes
Automated GSI flashing tool for Redmi Note 11 (spes)
I WON'T GIVE SUPPORT TO THOSE WHO FACE ISSUES BY NOT READING THE STEPS BELOW CAREFULLY!
I will get right into the topic here, find the answers to your questions below at near the end.
What this tool does:
1. Flash a GSI to your Dynamic partitioned Note 11
2. Patch your Vbmeta
3. Patch Product for magisk flashing
How to use this tool:
0. Flash a rom (stock rom, MIUI EU, AOSP, ...) - IMPORTANT
1. Download your GSI and the tool, extract them
2. Copy your GSI image to the tool's folder, rename the GSI to system.img if you are using Windows
3. Boot your phone to fastboot mode and plug it in
4. Run the "windows.bat" or "macos.sh" script based on your os
5. Wait until the process finishes, your phone will automatically reboot
Download: See attached file
Extras:
A ROM collection Telegram channel of mine, you can see screenshots of GSIs I booted on Note 11 by searching it there
The original post on Telegram
Credit:
kusti420 for Product file
AnhNotAnh (me) for the tool ofc
Main Q&A:
Q: What is a Generic System Image, GSI?
A: A GSI is a prebuilt system image that can be booted on devices that support Project Treble. In short, this System Image is a custom ROM but it uses your Vendor, Kernel from your previous/stock ROM.
Q: Okay, but why I would like to flash it on my Redmi Note 11?
A: As we have already known, MIUI does not perform exactly well in the recent years, especially on such a low end and underpowered phone. GSI helps us getting a taste of AOSP's cleanliness and smoothness before the developers finish making actual custom ROMs. This is a temporary solution, good enough to use, please don't think or complain if your GSI perform badly, since it is not a ROM or trying to be one either.
Q: Why do we need a dedicated tool and such time wasting thing to do? Can't you just flash it in a custom recovery?
A; From Android 10, devices with it come equipped with a new partition scheme, as known as Dynamic Partition. It helps speeding up OTA updates and make the partitions more flexible in size. But also creates a huge difficulty in flashing those GSI, that is why you cannot flash the image in a custom recovery.
Q: My terminal window freezes at a certain progress for too long! What should I do?
A: This case often happens with Windows users. Everything is quite complicated BTS, but the workaround is just spamming Enter key several times every minute or two.
Q: What if I want to install a GSI on top of another one? I already flashed one, do I need to restore my MIUI or AOSP rom to flash GSI?
A: It is not necessary, you can flash a new GSI on top. The tool will clear your previous GSI without erasing required stuff from ROM.
Q: My GSI does not boot, what should I do??
A: I highly suggest using GSIs based on Phh's work. Those are often called Phh GSIs. Secondly I would highly suggest against using "Ported GSIs", those are often based on Erfan or Xiaoxindada's GSI tool, they are a port from a different device's ROM instead of directly built from source like Phh. Here is a list of GSIs based on the man himself, Phh.
Q: Bro my phone just boot to TWRP and nothing happens, computer still waits for my device??
A: Like I said before, you can try spamming Enter key. It is also likely that your TWRP does not support Fastbootd (Fastboot Dynamic) environment, an easy workaround for this is using MIUI's boot (kernel) image, stock Fastbootd mode will be used.
Q: Which Android version can I flash??
A: You can flash corresponding or NEWER Android version GSI with the ROM you are coming from/installing GSI on top, you cannot flash a lower version one. For example, you can flash Android 11, 12, 12.1, 13, bla bla GSIs when coming from stock Android 11 MIUI ROM (Android 11 Vendor for people who understands)
Q: Can I use this tool on another device?
A: Yes, with proper bringup and changes in the tool for it to compatible with your device and it will work. But I will not be responsible for bricks, which I always won't xD
More questions and answers will be updated later.
Reserved.
Thanks for this Awesome Tool. Quiet Simple and efficient.
@PingVN This script works on Xiaomi redmi note 11 4g codename selene?
I've had my Moto G Stylus 5G rooted with magisk for a while now and just realized I can't write any system files, remove any system files or uninstall system apps. I have no idea where to start so any help at all or if someone could point me in the right direction?
Side note, this is my first thread ever so everything is new to me.
NOT responsible for bricked device!!! Proceed with caution and at your own risk. Linux/Ubuntu/debian is absolutely necessary for this process. No other ways for it.
NOT for the new Magisk v25 DO NOT DO THIS if you have installed Magisk v25 and have avb intact. Read the second paragraph again twice PLEASE!
Credit goes to NOT ME! ! ! ((Lebigmac has this
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
)(mines better in my opinion but I used his packages soo all to him everybody)) You should check these files out. Flash rw25.zip (I edited size of available space to agree with our ROM.) in twrp or OFox. An error will occur! Don't panic! Do not exit twrp/OFox. Unzip systemrw_1.32_bundle.zip in Linux/Ubuntu and run the sysrw script from the unzipped folder. From there it will dump your images from system, vendor, product, system_ext and create a super_fixed.bin(fastboot flashable) and then the script will flash to your device.
If you want clean then factory reset and wipe data, otherwise reboot and start uninstalling.
* warning *
If your device gets stuck in bootloop then flash stock vbmeta and vbmeta_system images with the flags --disable-verity --disable-verification. All will boot fine after that. (Again no Magisk v25. The new coding fails both ways.)
After all is said and done then start uninstalling packages, and or adding packages to your mounted /,/system,/vendor, etc by using terminal in recovery by advanced menu and mount then by typing
mount -o remount,rw /
" Same as above but with " /System_root, not /
Same as above but with /Product,. Etc,etc
After such you can add packages to product or system to get apps to install to system. Make sure you install the app first In android before you want to move it to system so it is initiated for your device
Just look in data/data in android os to find out which packages you should copy. (I check dates to see which of my apps I installed latest and go from there.) Then in twrp copy your apk and any lib or lib 64 to a newly created system/apps/selectedApp folder. after you copy the files, rename the folder you just copied to the system/product dir to the name of the app In camelBack type. That means the first word of the folder should all be lowercase and every word after that should start with a capital.
E.g. googleCalendar novaLauncher googleChromeBeta
So on and so on.
After everything wipe caches.
Whoop whoop!! All gravy baby now you can do anything your heart contents to.
((AGAIN I cannot stress this enough. NO MAGISK v25 NO No NO no NO No no!) Find another way for Magisk v25)
Don't forget to always make sure you have ArtiicPanda's skym3+ kernel flashed for the xt2131 otherwise a preformatted card may not be accepted or recognized and also touch may not work on your custom recovery. Just a reminder folks.
And of course I have Magisk v25 installed...
Daveed1013 said:
And of course I have Magisk v25 installed...
Click to expand...
Click to collapse
Just downgrade through twrp or OFox by removing Magisk and then installing the v24.1 apk just like a zip.
At least until a workaround is gotten tested and given out.
sosthenisRR said:
Just downgrade through twrp or OFox by removing Magisk and then installing the v24.1 apk just like a zip.
Click to expand...
Click to collapse
Everything I read was saying there wasn't a custom recovery for the moto g stylus 5g, could you point me in the right direction please?
Moto G Stylus 5g (2021) xt2131 only
Here is the page for the custom kernel you will need to flash.
[Kernel][1.6.2022] Sekiyama 1.3 for Moto G Stylus 5G "osaka"
Sekiyama-Kernel for Moto G Stylus 5G The kernel is based on sources from @Electimon which can be found here. Features: Main Features: - Based on kernel sources from Motorola - New performance based scheduler "dragrace" which prefers max clocks...
forum.xda-developers.com
And the recovery is at
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
1pwn.ixmoe.com
*Command*
fastboot boot twrp*.img (name of file)
Once in twrp go to advanced tab and tap on install recovery to ramdisk and then continue to flash the twrp.img from before.
If touch doesn't work you must flash the kernel to make sure touch is responsive.
Best way for that if you do not have an otg cable is to download
Franco's kernel manager and flash it in the app. Guaranteed to work.
DO NOT flash twrp with Franco kernel manager unless you know what you're doing. K peoples.
Custom roms cannot be flashed with recovery yet. Only the custom recovery will work to flash custom ROM onto custom ROM base. Do not try to flash custom ROM package with twrp over stock android. Got it, great, good.
Now,
Good luck and think smart. Read twice work once.
Oh yeah for those who do not know.
Moto g stylus 5g = Denver
And
Denver = osaka
So moto g stylus 5g (2021) xt2131 = osaka
Edit. Had a slight brain fart so deleted the post. My bad.
Well my Dell Precision got stolen so with no laptop to speak of I'll have to wait to try the new recovery.
i see there,s lot of threads avaliable about custom roms twrp and kernels
but there,s not guide for make custom rom for OP?
i also try many kitchen to unpack rom and try unpack but its even not able to unpack vendor system_ext etc
just unpack imgs via dumper tool but not able to unpack rom and mod to own way and flash
i also see xiaomi roms build for OP and OP for xiaomi but no way no guide etc
like if OP10 pro rom port to OP8 etc
is also try linux but same errors and also superr kitchen failed :L
for samsung kitchen avalible for cook roms but why not for this cow
is there any hope for my this dream or its just bury my dream