[KERNEL][Dispossible]A kernel for EMUI8.2 or ROMs based on EMUI8.2 - Honor Play ROMs, Kernels, Recoveries, & Other Deve

I just made few changes on the official open source kernel of 8.
Some features:
This kernel is based on the official open source kernel.
This kernel allows users to use "setenforce 0" or "setenforce 1" to change the status of selinux.
======FBI Warning======
It was only tested on my phone...
The phone is COR-AL10 and the system is offcial EMUI8.2 151.
I know it will not work on EMUI9 or other 9 systems.
I don't konw whether it could cause hardware damage to your phone.
=====================
Introducions:
1. Maybe we can backup the kernel first.(If you are brave, you can skip this step.)
I used the mt manager 2.0 (free editon) to copy the /dev/block/by-name/kernel_a to somewhere interesting.
Then we reboot the phone and hold the vol- to enter the bootloader mode.
2. We can use this command to flash the kernel.
Code:
fastboot flash kernel xxx.img
3. We can use this command to reboot.
Code:
fastboot reboot
4. If there are any problems after flashing this kernel, you could flash the official kernel or your backup kernel.
ps. Flashing kernel could not cause losing data. But I suggest you do a backup.
pps. Why we flash the kernel to change the selinux status? Because the official kernel don't allow user use the command "setenforce" to change the status. It means that the status must be "enforcing". Now you can use the command "setenforce 0" to make the SELinux interesting.
Source code:
https://github.com/kindle4jerry/honor-play-kernel-8.1-kindle4jerry
Download: maybe you can download it from my github
https://github.com/kindle4jerry/honor-play-kernel-8.1-kindle4jerry/releases/tag/0.2

Related

[Root][Stock][P2a42_S244][Fastboot]

You can flash this boot.img with fastboot on the latest stock ROM (S244) with an unlocked bootloader (no custom recovery needed).
The included Magisk is v13.6 (beta) and the Manager is v5.2.0.
From what I gather the modules won't install (or using something like Flashify won't work) because there are still f2fs bugs present (not only on this device, most android kernels have them). But I didn't fully test this so YMMV.
I did it this way because I only need root for some apps (like: Amaze, Termux, Wirebug, WiFiKeyShare, KISS launcher, ...) and didn't want to change too much after unlocking.
Don't ask about passing the SafetyNet check. I don't use Google Play Services so really can't answer this.
You can also do this yourself by following the instructions in the main Magisk thread. But I uploaded it as it's maybe of any use to somebody else that only needs a fast/simple (systemless) root solution.
DL-link:
https://www.androidfilehost.com/?fid=817550096634797229
Instructions:
Rename the downloaded image to boot.img and run the following commands from the same folder.
$ adb reboot bootloader
$ fastboot flash boot boot.img
$ fastboot reboot

Flash kernel to disable the selinux on EMUI9.0

If selinux is useless for you or you don't konw what is selinux, maybe you don't have to read the thread.
This is a kernel but I don't have have enough permissions to send it to the kernel section.
This kernel allows users to use "setenforce 0" or "setenforce 1" to change the status of selinux.
======FBI Warning======
It was only tested on my phone...
The phone is COR-AL10 and the system is offcial AEX of View 10.
I don't know whether it could work on L29 or official EMUI9.0.
I know it will not work on EMUI8 or other 8 systems.
I don't konw whether it could cause hardware damage to your phone.
=====================
Introducions:
1. Maybe we can backup the kernel first.
I used the mt manager 2.0 (free editon) to copy the /dev/block/by-name/kernel_a to somewhere interesting.
Then we reboot the phone and hold the vol- to enter the bootloader mode.
2. We can use this command to flash the kernel.
Code:
fastboot flash kernel xxx.img
3. We can use this command to reboot.
Code:
fastboot reboot
4. If there are any problems after flashing this kernel, you could flash the official kernel or your backup kernel.
ps. Flashing kernel could not cause losing data. But I suggest you do a backup.
pps. Why we flash the kernel to change the selinux status? Because the official kernel don't allow user use the command "setenforce" to change the status. It means that the status must be "enforcing".
Kernels & Imageslanzouyun...)
https://www.lanzous.com/i553l4d
Good luck and enjoy the kernel.
Maybe I have a new version
and I will upload it
Here is my new post and new version of kernel.
https://forum.xda-developers.com/ho...el-kernel-emui9-0-roms-based-emui9-0-t3972873

[GUIDE][TWRP][ROOT][FLASH] Xiaomi MI MIX3 5G Android 9 root, diagnostic port, codes

UNLOCK BOOTLOADER & ROOT DEVICE
1. Unlock Bootloader (Xiaomi procedure, 7 days via MI Unlock tool)
https://fossbytes.com/how-to-unlock-bootloader-on-xiaomi-devices-using-mi-unlock-tool/
2. Fastboot flash recovery TWRP and root the android 9 rom
(based on https://www.cyanogenmods.org/forums/topic/twrp-download-for-mi-mix-3-5g-and-rooting-guide/)
2.1 Install ADB for Windows and Xiaomi Drivers
2.2 Download TWRP for MI MIX3 5G Android 9 PIE - twrp-3.3.1-0-andromeda.img
https://androidfilehost.com/?fid=6006931924117900528
(based on https://forum.xda-developers.com/showthread.php?t=3941867)
2.3 Rename file to recovery.img and put it into ADB folder on Windows
2.4 Turn off the phone, Reboot to Fastboot (Volume Down + Power)
2.5 Plug the phone into computer
2.6 Open Windows CMD
2.7 Go to your ADB directory
2.8 Type the commands in cmd
cd C:/adb
fastboot devices
fastboot flash recovery recovery.img
2.9 Download Disable Force Encryption and Magisk Zip
https://www.cyanogenmods.org/downloads/disable-force-encryption-twrp-flashable-zip-treble/
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2.10 Copy the files to USB memory stick formatted to FAT32, you should have two files:
Magisk-v20.3.zip
DisableForceEncryption_Treble.zip
2.10 Turn on phone to recovery (Volume Up + Power)
2.11 Go to Menu > Wipe > Format Data > "yes" (this will format the data)
2.12 Go to Menu > Advanced > Fix Contents
2.13 Plug in your USB stick with files via OTG USB C connector
2.14 Go to Menu > Install > Select Storage > OTG
2.15 Select Magisk-v20.3.zip
2.16 Add more zips and select DisableForceEncryption_Treble.zip
2.17 Flash the zips and reboot device
UPDATE FOR TWRP
To gain root you may now only boot the recovery instead of flashing and proceed with flashing Magisk and Disable Force Encryption.
# fastboot boot recovery.img
TWRP 3.3.1-1 Xiaomi Mi Mix 3 5G (andromeda) by mauronofrio:
- Added Android 10 Support;
- Fixed compatibility.zip errors;
- Make the TWRP able to boot directly from fastboot;
- Removed TWRP app;
- Added dtbo and persist target to flash image menu;
- Fixed some problems with Stock ROMs flashing.
Download TWRP: https://androidfilehost.com/?fid=4349826312261701065
Thanks to @mauronofrio
## QUALCOMM DIAGNOSTIC PORT AND TOOLS
(based on https://forum.xda-developers.com/oneplus-7-pro/help/force-enable-volte-vowifi-t3934227)
1.1 Download
https://androidfilehost.com/?fid=11410963190603864074
https://androidfilehost.com/?fid=11410963190603912872
QPST_2.7.474.zip
QUD.WIN.1.1 Installer-10037.3 Setup.zip
Just use the standard settings and click on OK, next,
1.2 OPEN DIAGNOSTIC PORT FOR THE SESSION FOR QPST (WINDOWS CMD ADB)
cd C:/adb
adb devices
adb shell
su (you need to add root permisions on android screen)
setprop sys.usb.config diag,serial_cdev,rmnet,adb
1.3 Once The Port is up you can use your Qualcomm Tools.
1.4 For example you can change the VOLTE/VOWIFI settings with PDC Tool
Select your device, right click on "Commercial" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
## FORCE ENABLE VOLTE AND VOWIFI BUTTONS IN ANDROID
cd C:/adb
adb devices
adb shell
su (you need to add root permisions on android screen)
setprop persist.dbg.ims_volte_enable 1; setprop persist.dbg.volte_avail_ovr 1; setprop persist.dbg.vt_avail_ovr 1; setprop persist.dbg.wfc_avail_ovr 1
######################## CODES FOR THE DIALER #####################
1. Diagnostic codes:
*#*#6484#*#*
2. Testing
*#*#4636#*#*
3. Calendar
*#*#225#*#*
4. Google Play services
*#*#426#*#*
5. Rlz Debug Ul.
*#*#759#*#*
6. Imei Information
*#06#
Enter these codes into the Dialer to enable the options in Settings. (Settings < SIM Cards & mobile networks < Sim Card Settings < VoLTE Enabled/Make Calls using WLAN) . THEY ARE ENABLED BY DEFAULT
VoLTE *#*#86583#*#*
VoWIFI *#*#869434#*#*
##### FLASH ROM AGAIN IF ANYTHING FAILS VIA FASTBOOT ###
01. You need to have unlocked bootloader
02. Download latest ROM based on your model (mine is 5G EEA n78)
Mi MIX 3 5G EEA Stable Fastboot V10.3.21.0.PEMEUXM 9.0 Download 2.5 GB
https://xiaomifirmwareupdater.com/miui/andromeda/
03. Download Mi Flash Tool
https://www.xiaomiflash.com/
04. Open the Mi Flash Tool, install drivers (if the install fails go to Mi Flash directory and create folder logs and log; open app again and install drivers)
05. Unpack the rom fastboot tgz
06. Select the Folder where the rom is unpacked (it should containg numerous of flash files)
07. Tick the Clear Data at the bottom (don't choose the clear data and lock cause it will lock your bootloader again)
08. Turn off the phone, Reboot to Fastboot (Volume Down + Power)
09. Plug the phone into computer
10. Click refresh, phone should be visible
11. Click flash
12. After successfull flash there could be an error fastboot lock (don't bother since you want to be unlocked)
13. If you want root flash twrp and magisk again
Thank you so much for this guide! Can I flash gsi rom with this? Sorry for the noob question
Jktfong said:
Thank you so much for this guide! Can I flash gsi rom with this? Sorry for the noob question
Click to expand...
Click to collapse
I have not tried to load the GSI ROM on that model. I guess there was some other topic under ROM development opened for that
https://t.me/mimix3_5G feel free to join this telegram group chat if you need any help we are all running a custom gsi with aosp 9 and 10 (pixel experience) @mxtuu222
Since last 20.1.9 update lost ecryption in twrp. Installed the latest 3.3.1.1.perseus. since then got loops to twrp. But if i try to launch
fastboot boot C:\mimix\twrp-3.3.1-1-perseus.img it boots to the system.
How to fix it?
dont want to use my PC to start the system every time.
Regards
Most probably you get bootloop, because after the update the partition was encrypted, you need to either flash DisableForceEncryption_Treble.zip or make a backup and install fresh OS with the guide from scratch,
Hey. help me with my problem inversion of the axes of the accelerometer https://forum.xda-developers.com/android/help/inversion-rotated-x-y-axes-accelerometer-t4059277
flash persist did not help me
Root Mix 3 5G
Hello,
i have some problems at point of rooting. my phone accept twrp recovery it's fully working and stays as recovery but when i try to istall magisk 20.4, 19.3 or whatever it will stuck at Mi screen and won't boot. when i reflash original boot img it will boot again but no root. can someone help me?
thank you
Thank you so much for this guide Without it I would have gone a little crazy trying to do a simple reset and update of my phone Saved for reference and I always come back.

[KERNEL][Dispossible]A kernel for EMUI9.1 or ROMs based on EMUI9.1

Add some new functions! --2020-03-18
Some features:
This kernel is based on the official open source kernel.
This kernel allows users to use "setenforce 0" or "setenforce 1" to change the status of selinux.
And in permissive version, the selinux will be set to permissive status when booting. The enforcing version will be set to enforcing when booting BUT you can unlock the selinux manually using setenforce 0 command.
(Some system don't allow the kernel set permissive when booting)
(Some ROM need permissive booting, like EvolutionX based on PHH)
This kernel unlock some schedulers of CPU and GPU which were hidden.
Add schedutil governor. IF you use the sched version, you should use this magisk module https://github.com/kindle4jerry/970EAS/releases
Or the default value of the schedutil is too stupid.
======FBI Warning======
The phone is COR-AL10 and the system is EMUI9.1.312 or some systems based on 312.
I don't know whether it could work on L29 or other official EMUI9.1.
I know it will not work on EMUI8 or EMUI9.0.
I don't konw whether it could cause hardware damage to your phone.
=====================
Introducions:
1. Maybe we can backup the kernel first.(If you are brave, you can skip this step.)
I used the mt manager 2.0 (free editon) to copy the /dev/block/by-name/kernel_a to somewhere interesting.
Then we reboot the phone and hold the vol- to enter the bootloader mode.
2. We can use this command to flash the kernel.
Code:
fastboot flash kernel xxx.img
3. We can use this command to reboot.
Code:
fastboot reboot
4. If there are any problems after flashing this kernel, you could flash the official kernel or your backup kernel.
ps. Flashing kernel could not cause losing data. But I suggest you do a backup.
pps. Why we flash the kernel to change the selinux status? Because the official kernel don't allow user use the command "setenforce" to change the status. It means that the status must be "enforcing". Now you can use the command "setenforce 0" to make the SELinux interesting.
Source code:
https://github.com/kindle4jerry/honor-play-kernel-9.1-kindle4jerry
Download: maybe you can download it from my github
https://github.com/kindle4jerry/honor-play-kernel-9.1-kindle4jerry/releases
Can I ask you to send me the output of this command? I would like to know what partitions are in EMUI 9.1
Code:
adb shell fdisk -l /dev/block/mmcblk0
Safetynet
Can you make a version of the kernal
with the bootloder unlocked warning on boot removed?
skvorecoo12 said:
Can I ask you to send me the output of this command? I would like to know what partitions are in EMUI 9.1
Code:
adb shell fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
It is dangerous. Because Huawei has no 9008 mode, forget it....
NIKHIL JOHN said:
Can you make a version of the kernal
with the bootloder unlocked warning on boot removed?
Click to expand...
Click to collapse
Ummm, it looks like that the warning words is in the bootloader.... I have heard that kirin can remove the warning, but it has to edit the bootloader, it is
too dangerous

[ROM][UNOFFICIAL][12][S]LineageOS 19.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Which GApps would you suggest?
I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.
Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.
I've set the state of the development to BETA due to quite good overall performance.
After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.
I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0
I'll take a look into it asap. Please be patient.
I can't find any reason for the crash; I'm sorry.
New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.
New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2
Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.
New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022
Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?
kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?
Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check
Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..
Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.

Categories

Resources