KernelSu For P20 lite (hi6250) that also support Erofs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KernelSU is a root solution for Android devices, it works in kernel mode and grant root permission to userspace application directly in kernel space. More information about KernelSU from here
Spoiler: information about Erofs
Erofs GSI refers to a Generic System Image (GSI) that is based on the EROFS (Extendable Read-Only File System) file system. The EROFS file system is a Linux-based file system that was developed by Huawei and was first introduced in the Linux kernel version 4.19.
The EROFS file system is designed to be an efficient, high-performance file system that is optimized for read-only scenarios. It uses a compression algorithm to compress data on the file system, which reduces the amount of storage space required and improves read performance. The EROFS file system also uses a hierarchical indexing structure to improve file lookup performance. Overall, the EROFS GSI is designed to provide improved read performance and reduced storage space requirements, making it a potentially useful option for developers and users who want to create or use custom Android firmware images
Changelog :
24-4-2023 version
Update to Kernel 4.9.319
Fix module load
23-4-2023 version
Fix Wifi issues
22-4-2023 version
sync. with kernelsu 0.5.5
21-4-2023 version
Initial release
DownloadKernelSu for P20 lite that support Erofs (it support ext4 as well)DownloadSOURCE CODE
Spoiler: Installation
1- Flash the kernel form Fastboot or TWRP
- fastboot flash kernel kernelSu.img
2- install kernelsu manger App form here or here
Spoiler: older versions
1- Kernel 4.9.319 (KernelSu not working)
Spoiler: older versions
Download
SOURCE CODE
2- Kernel 4.9.148 Harmony os 2 based (KernelSu not working)
Download
Download permissive
Source code
Spoiler: How to get Erofs GSIs
You can convert any GSI to Erofs using this script
OR
@AltairFR has developed A13 Erofs GSIs
1-TrebleDroid-GSI from here (evn or egn)
2- Arrow from here
* arm64_evN : ARM64 A/B erofs lz4 compression read-only - Vanilia with no SU
*. arm64_egN : ARM64 A/B erofs lz4 compression read-only - Google Apps with no SU
update
Kernel now support KernelSU
Thank you will test and report back
The kernel works just fine but I have no idea how to install the actual su program xD
frituurvet said:
The kernel works just fine but I have no idea how to install the actual su program xD
Click to expand...
Click to collapse
There's kernelsu app similiar to magisk, it's easy to miss it in github releases: https://github.com/tiann/KernelSU/releases/download/v0.6.0/KernelSU_v0.6.0_10981-release.apk
also @Abdelhay.ali turex released .337, your github is still on .319 FYI
FYI I couldn't wait for an update so I updated it myself. I posted .337 with latest kernelsu (11023) to phenix thread.
[KERNEL][EMUI 9][P20 lite] Phenix kernel
PHENIX KERNEL Disclaimer: Use this kernel at your own risk. Flashing it may brick your device. I'm not responsible for any software/hardware and any kind of damages/losses. NOTE : Use only on EMUI9 base(stock or custom) REQUIREMENTS ...
forum.xda-developers.com
Related
[BETA] MAGISK V19.3 & MAGISK MANAGER V7.2.0 FOR PHOENIX OS V3.5.0 OFFICIAL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk Manager is best SuperSU app you can got lot's of future with magisk manager. Magisk v19.3 & Magisk Manager v7.2.0 Working Good On Phoenix OS v3.5.0 Official.
Changelog:
Magisk v19.3-
- [MagiskHide] Hugely improve process monitor implementation, hopefully should no longer cause 100% CPU and daemon crashes
- [MagiskInit] Wait for partitions to be ready for early mount, should fix bootloops on a handful of devices
- [MagiskInit] Support EROFS used in EMUI 9.1
- [MagiskSU] Properly implement mount namespace isolation
- [MagiskBoot] Proper checksum calculation for header v2
Magisk v19.2-
- [General] Fix uninstaller
- [General] Fix bootloops on some devices with tmpfs mounting to /data
- [MagiskInit] Add Kirin hi6250 support
- [MagiskSU] Stop claiming device focus for su logging/notify if feasible: This fix issues with users locking Magisk Manager with app lock, and prevent video apps get messed up when an app is requesting root in the background.
Magisk v19.1-
- [General] Support recovery based Magisk
- [General] Support Android Q Beta 2
- [MagiskInit] New sbin overlay setup process for better compatibility
- [MagiskInit] Allow long pressing volume up to boot to recovery in recovery mode
- [MagicMount] Use proper system_root mirror
- [MagicMount] Use self created device nodes for mirrors
- [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)
Magisk Manager v7.2.0-
- Huge UI overhaul
- More sweet changes coming in the future!
Magisk Manager v7.1.2-
- Support patching Samsung AP firmware
- Much better module downloading mechanism
Apk Info:
• Name: Magisk Manager
• Version: v19.3 & v7.2.0
• Packed: com.topjohnwu.magisk
• File Size: 8.22 MB+2.5 MB
• Updated: 05-Jun-2019
• Developer: Topjohnwu
• Requires: Android 5.0 and up
• Supported Language: English
How to update:
1. Copy the initrd.img & ramdisk.img into the PhoenixOS system folder.
2. Clean the system(root)/data/adb folder.
3. Install/Update magisk Manager application. (After update: Clean magisk Manager data. *settings>apps>magiskmanager)
4. Connect the internet and run magisk Manager. Install the additional files. This much
Merci pour votre aide et pour le partage des étapes et l'explication des procédures
What's the point of that thread? We already have a topic for Magisk in the corresponding forum: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Closed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Prerequisites
1. Unlocked bootloader.
Instructions
https://telegra.ph/How-to-install-TWRP-Team-Win-Recovery-Project-10-20
XDAevDB Information
TWRP Recovery, Tool/Utility for the Umidigi A3 / N
Contributors
Hadenix, TeamReloaded
Version Information
ROM OS Version: 9.0 Pie
Status: Stable
Based On: TWRP
Current Stable Version: 3.3x
Downloads: TWRP_by_Hadenix
SUPPORT:
Unofficial Telegram Channel
20-10-19
- Correction of minor errors
- New TWRP Welcome Screen
- Support A/B feature for EMMC and UFS boot region
- Derganje corrected at the beginning of launch/thank you nemo-nemo for the tip
- Added system/vendor for backstop
- The screen goes off and is locked
- Added system/vendor mounted as drives/thank you Alekcandp
- Change Device Code Name
- MTP works
- Core from the firmware A3_N_V1.4_20190715
- Work has been done to install OTA updates for drain firmware A3_N
- Excluded from TWRP APP assembly
- ADB works
- Updated sources to 9.0.0 r47
- Added to firmware recovery_dtbo.img assembly 1.4
- Added a flag to keep the backstops in the TWRP/BACKUPS/phone model folder
- Recycled BoardConfig and sorted
- First release
is this at all useable for the a3 pro variant?
Ciao, are there any risks in the procedure? is it enough to have the root?
signature verification failed
Hello XDA developers
When i try to install any zip files (supersu, magisk, no-verity-opt-encrypt) with Android recovery, it return E:failed to verify whole-file signature.
I would like to know if the recovery installed is unoficial twrp or not, because I tried to install it and it doesn't look too much like TWRP.
I can't find the official TWRP for my UMIDIGI A3 N.
zermi said:
signature verification failed
Hello XDA developers
When i try to install any zip files (supersu, magisk, no-verity-opt-encrypt) with Android recovery, it return E:failed to verify whole-file signature.
I would like to know if the recovery installed is unoficial twrp or not, because I tried to install it and it doesn't look too much like TWRP.
I can't find the official TWRP for my UMIDIGI A3 N.
Click to expand...
Click to collapse
Hello,
I know Im a bit late but this thread has helped me to install i think a custom twrp on my Umidigi A3
https://community.umidigi.com/forum.php?mod=viewthread&tid=2962
Hadenix said:
20-10-19
- Correction of minor errors
- New TWRP Welcome Screen
- Support A/B feature for EMMC and UFS boot region
- Derganje corrected at the beginning of launch/thank you nemo-nemo for the tip
- Added system/vendor for backstop
- The screen goes off and is locked
- Added system/vendor mounted as drives/thank you Alekcandp
- Change Device Code Name
- MTP works
- Core from the firmware A3_N_V1.4_20190715
- Work has been done to install OTA updates for drain firmware A3_N
- Excluded from TWRP APP assembly
- ADB works
- Updated sources to 9.0.0 r47
- Added to firmware recovery_dtbo.img assembly 1.4
- Added a flag to keep the backstops in the TWRP/BACKUPS/phone model folder
- Recycled BoardConfig and sorted
- First release
Click to expand...
Click to collapse
hello! do you still have the twrp device tree?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
MEGA : TWRP_3.5.1
Flashing
Recovery : Download Recovery.img file from link and flash it through your current recovery in recovery Partiton
ODIN : else pack recovery img in .tar and flash it through ODIN in AP.
Changelog
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Credits
all goes to @Astrako for his hard work with all exynos7870 device trees without him this would not be possible
Device trees : https://github.com/samsungexynos7870
7870 Group : https://t.me/samsungexynos7870
PrishSupport : https://t.me/prishsupport
PrishChannel : https://t.me/prishupdates
TWRP : https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Note : Test it and if you found any issue do let me know by PMing me on telegram @neel0210 .
Reserve
What happened with this project? Link is down
New link?
link not work.....??????????????? pls
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
MEGA : TWRP_3.5.1
Flashing
Recovery : Download Recovery.img file from link and flash it through your current recovery in recovery Partiton
ODIN : else pack recovery img in .tar and flash it through ODIN in AP.
Changelog
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Credits
all goes to @Astrako for his hard work with all exynos7870 device trees without him this would not be possible
Device trees : https://github.com/samsungexynos7870
7870 Group : https://t.me/samsungexynos7870
PrishSupport : https://t.me/prishsupport
PrishChannel : https://t.me/prishupdates
TWRP : https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Note : Test it and if you found any issue do let me know by PMing me on telegram @neel0210 .
Is it possible to have a mod so that system will auto mount
o arquivo esta fora do ar se tiver como concertar estou precisando
Translated by GT: the file is down if you have a way to fix it I need it
the link is broken
Czy Czy mogę go z flashować na Samsunga Galaxy Sm- j600fn/DS?
Mod translation: Can I flash it from Samsung Galaxy Sm-j600fn / DS?
Stock kernel with upstream exFAT driver for Pixel 4/XL
Background
Read about the Google Pixel 6/Pro getting official exFAT support in Android 13 on an Esper article and dug around the source code for Android's vold. Seems like Android has "supported" exFAT since Pie/9 with this commit in platform/system/vold as long as the device comes with 1) exFAT driver in the kernel, 2) mkfs.exfat and fsck.exfat in /system/bin(weird that Google doesn't include this in Android). Thankfully, both are available for all devices with Linux kernel > 4.1 through the linux-exfat-oot exFAT driver and exfatprogs, both provided by the official Linux exFAT driver maintainer, Namjae Jeon. Some compilation and git clone-ing later and, here we are!
Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Features
-Supports accessing exFAT disks in Android as you would a FAT disk
-Kernel built from the latest July security patch sources from Google, completely stock apart from exFAT driver and some debugging disabled
-exFAT kernel driver backported from Linux kernel 5.19.1
-exfatprogs built from master branch of namjaejeon/exfatprogs
-Kernel compiled with AOSP Clang 12.0.5, exfatprogs compiled with Android NDK r23
-Kernel built with CFI/LTO enabled and reduced debugging(floral_exfat_perf_defconfig)
Requirements
-Unlocked Bootloader
-Magisk
-Recovery or EX Kernel Manager/FKM app
Download
-Attachments below
How to install
1a. Download the kernel flashable zip(floral-stock-kernel-jul22-exFAT.zip or floral-stock-kernel-jun22-exFAT.zip depending on whether you are on July update or June update)
1b. Download the Magisk module zip(magisk-exfatprogs-aarch64-v1.zip)
2a. Install the Magisk module zip from Magisk app
2b. Flash the kernel zip in EX Kernel Manager or FKM app or in TWRP/Lineage Recovery
3. Connect an exFAT disk and try it out!
Source code
https://github.com/haoyangw/android_kerrnel_google_floral
Credits
- Namjae Jeon(exFAT driver maintainer)
- Google(for kernel sources)
- topjohnwu(for Magisk)
- osm0sis(for AnyKernel3)
- nathanchance(for his Github guides on compiling Android kernel with Clang)
- Zackptg5(for his MMT-Extended repo used for my Magisk module zip)
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog
17-Dec-22
- Latest Android 13 kernel source for Pixel 4/XL
- October security patch
11-Jul-22
- First release
- Added exFAT driver as git submodule under Google's stock kernel sources
- July security patch
- Disabled some kernel debugging code
[Guide] How to port this to other Android devices
Requirements
- Android phone with Linux kernel >= 4.1
- armv7 or arm64 SoC/CPU
- CLI experience and a Linux PC with decent RAM/CPU for compilation
Points to note
- LTO/CFI takes a huge amount of RAM if your PC's CPU has a lot of cores since the LTO operations are parallelised. I couldn't find a flag to disable parallelisation/multi-threading of LTO so I had to enable ZRAM to give lld enough RAM. For me, I had a 4-core/8-thread CPU(Intel Core i7-8809G) with 32GB RAM and lld managed to eat up 19GB-25GB RAM(Jun security patch took 19GB, Jul security patch took 25GB before lld got killed due to OOM, didn't check RAM usage on successful compilation) when run with make -j2
Steps
1. Download your device's kernel sources
2. Add namjaejeon/linux-exfat-oot to fs/exfat under the kernel source, either as a git submodule or just download the repo as a zip and extract it
3. Perform steps 2 & 3 of jamjejeon's guide
4. Enable the exFAT driver by running 'make ARCH=<device architecture> <defconfig file>' and 'make ARCH=<device architecture> menuconfig', and then going to 'File systems' -> 'DOS/FAT/NT Filesystems' -> Press 'Y' key of your keyboard after moving the highlighted option to 'exFAT filesystem support'
5. Compile your kernel
6. Take the generated Image(.lz4)(-dtb) and dtbo.img files and use AnyKernel3 to generate a flashable zip
7a. Install either the 'magisk-exfatprogs-aarch64-v1.zip' or 'magisk-exfatprogs-armv7a-v1.zip' file attached below, depending on whether your device is 64-bit(aarch64) or 32-bit(armv7-a)
7b. You can also cross-compile exfatprogs from source by setting up the Android NDK according to Google's Use NDK with other build systems guide(autoconf section)
This too
Sorry for the delay, here's the latest stock kernel with exFAT support added for those on the final update of Pixel 4/XL, Android 13 October patch! Installation steps are the same as before. I'm not sure whether it'll support earlier stock Android 13 builds though, try at your own risk! Hope this is useful!