Kernel 3.18 [CAF Q] - Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth

What is this kernel project ?
Xioami make daisy Q stock kernel brocken . , this project is designed for share kernel CAF Q for stability and safety kernel updated for your devices
What is features added in this Kernel caf daisy q 3.18 ?
Merged caf tag 'LA.UM.8.6.r1-04600-89xx.0
added caf tag prima wlan 'LA.UM.8.6.r1-04600-89xx.0 in source
@33bca CAF kernel rebased
*merged LA.UM.8.6.r1/fixes
*branch 'aosp/android-3.18' merged
*latest security patch google merged
*exfat driver
*upstream mismerge fix
*qcom mismerge
*touchscreen : updated driver fts from daisy-q-oss
*hqsysfs added
*tcp : set improvement to initial 64k
*preserve memory on restart
* Disabled dm-verity and Force vendor encryption
* Only build daisy dtb ( why build dtb for other device... )
And probably more change missed check source for more info
Compatible Systems with this Kernel
* this kernel is designed by xiaomi for daisy android 10 stock rom , so its mean this kernel work too in @phhusson gsi system
Guide Install :
1) Boot into TWRP recovery
2) decrypt your storage
3) Flash the Kernel ZIP file & re-flash magisk if installed
Reboot to System- enjoy!
DOWNLOAD
Thanks for :
C.A.F
@33bca
-and all other no mentionned in sources
XDAevDB Information
Kernel DAISY Q 3.18 for Mi A2 Lite (daisy)
Contributors :
@ada12 @33bca
Source Code: https://github.com/Aarqw12/kernel_xiaomi_daisy-1
Status: Stable
Current Stable Version: LA.UM.8.6.r1-04600-89xx.0
Stable Release Date: 2020-06-23

2020/04/13 update
*merged caf tag LA.UM.8.6.r1-04200-89xx.0 & prima caf tag LA.UM.8.6.r1-04200-89xx.0
Merge remote-tracking branch 'aosp/android-3.18' into LA.UM.8.6.r1
driver leds :
*aw2013&aw2023 driver update from daisy-q-oss
*Change leds-qpnp-flash from daisy-p-oss and enabled
*Enabled Serial Number Proc Interface
2020/04/23 update
merged prima caf tag LA.UM.8.6.r1-04600-89xx.0

It ran smoothly! Thank you!!

KERNEL reuploaded rebased in 100% caf project kernel for avoid all change damaged by xiaomi in daisy-q-oss

Run great, but only one problem for me... Not working Swipe with fingerprint for notification.

swipe fingerprint need support in system:crying: ...
Buddy_888 said:
Run great, but only one problem for me... Not working Swipe with fingerprint for notification.
Click to expand...
Click to collapse

Anyone already try with phhusson GSI ?

I use phhusson gsi ,no any problems ...
gusbalaa said:
Anyone already try with phhusson GSI ?
Click to expand...
Click to collapse

after another report, xiaomi have no delete support fp gestures its just fp goodix gestures is no good for system. I have updated link witch fix for goodix gestures ...
Buddy_888 said:
Run great, but only one problem for me... Not working Swipe with fingerprint for notification.
Click to expand...
Click to collapse

ada12 said:
What is this kernel project ?
Xioami have make daisy Q stock kernel brocken and can damage permanently your phone ... , this project is designed for share kernel c.a.f Q for stability and safety kernel 3.18 Q for your devices
What is features added in this Kernel stock caf daisy q 3.18 ?
Merged caf tag 'LA.UM.8.6.r1-04000-89xx.0
added caf tag prima wlan 'LA.UM.8.6.r1-04000-89xx.0 in source
@33bca CAF kernel rebased
*merged LA.UM.8.6.r1/fixes
*exfat driver
*adreno properly set GPU timeout
*upstream mismerge fix
*cpufreq governor improvements added
*qcom mismerge
*touchscreen : updated driver fts from olive-p-oss
*tas2557 codec sound added
*hqsysfs added
*TTL fix included
*tcp : set improvement to initial 64k
*preserve memory on restart
* Disabled dm-verity and Force vendor encryption
* Publish charger voltage to the usb psy :
-This brings back the "Charging slowly", "Charging" and "Charging
rapidly" texts on the lock screen.
Contributors :
@ada12 @shivamkumarJha
Click to expand...
Click to collapse
Will this kernel fix issues related to the bricking of daisy phones once updated to the Android 10 os v11?
Or is it for only d gsi & cfw for daisy?
Thanks

ada12 said:
I use phhusson gsi ,no any problems ...
Click to expand...
Click to collapse
Everything is fine right ?

1) this kernel fix issue for bricking in stock ROM v11
2) can be used too for gsi only after stock v11 ...
agbadino said:
Will this kernel fix issues related to the bricking of daisy phones once updated to the Android 10 os v11?
Or is it for only d gsi & cfw for daisy?
Thanks
Click to expand...
Click to collapse

I use since some day and in my device I no see any issue ...
I no need modify kernel actually ...
gusbalaa said:
Everything is fine right ?
Click to expand...
Click to collapse

ada12 said:
1) this kernel fix issue for bricking in stock ROM v11
2) can be used too for gsi only after stock v11 ...
Click to expand...
Click to collapse
Thanks so much for ur response.
But how do i use it in order to avoid bricking my device if i choose to update to Android 10 using miflash?
Thanks...

guide flash v11
1)go in stock recovery format data reboot to fastboot
2) flash in miflash Android 10 update( ./flash_all_except_storage ) and reboot immediatly to fastboot again!
3) enter : fastboot boot twrp.img (link ), in twrp mount vendor,system , flash force disable encryption( link ) and kernel.zip
4) you can safety reboot to system
ps : run always your device in fastboot unlocked its keep your device safe to brick if update fail you can always re-flash in fastboot or reboot to edl without pin edl
agbadino said:
Thanks so much for ur response.
But how do i use it in order to avoid bricking my device if i choose to update to Android 10 using miflash?
Thanks...
Click to expand...
Click to collapse

I appreciate u taking time to explain.
ada12 said:
1)
ps : run always your device in fastboot unlocked its keep your device safe to brick if update fail you can always re-flash in fastboot or reboot to edl without pin edl
Click to expand...
Click to collapse
I guess i understand wat u mean. Always keep d phone in fastboot mode.
However while i cant tell apart d different possible variants of "mi a2 lite" phone, i have observed that mine while using miflash, flashing any rom doesnt succeed unless i put it in "EDL" mode.
Also can i get a possible link for the stock Android 10 fastboot rom download? Thanks

- for flash rom you have no variant "mi a2 lite" ( all different part is included in rom )
link fastboot v11 ( link unofficial its v10.0.18 + ota recovery extracted and all img added inside )
agbadino said:
I appreciate u taking time to explain.
I guess i understand wat u mean. Always keep d phone in fastboot mode.
However while i cant tell apart d different possible variants of "mi a2 lite" phone, i have observed that mine while using miflash, flashing any rom doesnt succeed unless i put it in "EDL" mode.
Also can i get a possible link for the stock Android 10 fastboot rom download? Thanks
Click to expand...
Click to collapse

v11.0.4.0
bootloop
no magisk modules etc..

Wiped dalvick cache ?
remained said:
v11.0.4.0
bootloop
no magisk modules etc..
Click to expand...
Click to collapse

oops..?
Please include wiping in the instructions!
and thanks <3

Related

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30
Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse
Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)
Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I
Thanks, I hope you don't forget dsds variant.
It is a pleasure to have SunKernel in LineageOS.
Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.
Flashing lineage and kernel, looking forward to try it
Thanks for upload
s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install
zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.
L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks
zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

[KERNEL][r6.1/r1]Reviver Kernel [7.1/9.0][08 Dec 2018]

Introduction
NOTE:
Hello everyone, this is my first kernel for the Moto G4 Plus. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Here are the major features of the kernel (feel free to explore Github)
Update to date with the latest Linux upstream version (3.10.108-EOL)
Westwood as the default congestion algorithm with many more to choose from
Several subsystems converted to use power efficient workqueues
Compiled with Google's arm-eabi 4.9 toolchain
Audio control from flar2
Downloads
Oreo 8.0 : https://sourceforge.net/projects/babyfish-kernel/files/athene/oreo_caf/
Nougat 7.1 : https://sourceforge.net/projects/babyfish-kernel/files/athene/nougat_caf/
Nougat 7.0 Stock :https://sourceforge.net/projects/babyfish-kernel/files/athene/stock_nougat/
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is unified for Moto G4 and the Plus variant so everything should be working fine.
Install the latest adb and fastboot: https://developer.android.com/studio/releases/platform-tools.html#download
Grab the boot image from the download links above
Method 1:
Using adb and fastboot
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Reboot and profit!
Method 2: TWRP
Keep the bootimage on your phone's storage and boot to TWRP.
Install > Select Install Image > Choose the image > Boot partition > Reboot
Changelog
28 November 2017
Oreo-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Nougat-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Stock N:
Code:
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (if you want a specific mention, please let me know)
All of you guys for viewing the thread
Thiago Neves @lcrd512 and Abhijeet Bohra.
Kernel source links.
8.0.0 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/oreo_caf
7.1 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/nougat_caf
7.0 Stock :
If you like my work, buy me an Appy Fizz or whatever you like
https://www.paypal.me/tywinlannister7 :good:
XDA:DevDB Information
Reviver Kernel, Kernel for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: https://github.com/tywinlannister7/android_kernel_motorola_msm8952
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-28
Last Updated 2018-12-10
Screenshots
Some Screenshots
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing. ?
tywinlannister7 said:
Some Screenshots
Click to expand...
Click to collapse
Which ROM is this?
Ayan Uchiha Choudhury said:
Which ROM is this?
Click to expand...
Click to collapse
DU 12 oreo
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Thanks for the new addition in the family.
I hope this will be the favorite member of the family:laugh:
Where is the love for stock user?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
There is a link for stock rom in the op though?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
Stock version won't be released any sooner. I don't have the time for it right now and compilation process of stock kernel is a bit different than CAF kernels. Maybe before the second week of January.
briatide said:
There is a link for stock rom in the op though?
Click to expand...
Click to collapse
Empty as of now
ganeshkmr21 said:
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Click to expand...
Click to collapse
IDK I don't have the time, we already have so many ROMs available. Creating a new ROM will be adding it to the huge list already available, from AOSP to LineageOS to Dirty Unicorns. I would rather work on optimizing what we have. Quality > Quantity.
jyoti.id said:
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing.
Click to expand...
Click to collapse
Yes. 7.1 version for all N custom ROMs and 8.0 for all the O custom ROMs
DU 12 oreo
Blueman1990 said:
DU 12 oreo
Click to expand...
Click to collapse
about DU 12 oreo where can i get it ?
many thanks
i love new system
Does not boot on LOS15. Can anyone else confirm? Cant do logs cause my data port on my phone is broken. It sits on the boot screen like its loading but never fully boots.
Thank you bro!! finally an oreo kernel!
Where I can get DU 12?
Does this have color management?
And which kennel manager should i use with this?
Thanks
harshal2234 said:
Where I can get DU 12?
Click to expand...
Click to collapse
Its not out yet I guess
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Ashishliterally said:
Does this have color management?
And which kennel manager should i use with this?
Thanks
Click to expand...
Click to collapse
Bro its just a 2 page thread. At least read. That question has been answered, in the OP!
Can't I get the unofficial build?
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Same for me. On LOS 14.1, XT1643
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
I don't think so. If magisk is installed/flashed once, then no need of flashing ever again until you freshly install the rom. (AFAIK)
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
Same happened with me I was on Invicta os 8.0

[ROM][Mi5][7.1.2][EAS] JDC Nougat Revived

Hey there,
good news for everyone who is missing the great JDC Nougat!
With smeroni68's authorization I'm offering you the latest version of the ROM, built from source, with some changes to keeping it up to date and maintained.
These changes are:
Latest security bulletins and changes from AOSP​Kernel upstreams from Linux Stable​Updates from Code Aurora Forum (CAF)​Some smallish modifications of standard apps or behavior​
All credit goes to the JDC team!
(Check attachment for a list of team members).
They are the geniuses behind this awesome ROM and kernel, and I'm only making basic and minor modifications to it.
Besides a huge thanks to each member of the JDC team, thanks to Google, Lineage, Linux, CAF, Github & everyone else involved!
And many thanks also to DennySPB who helped me a lot with all the building stuff!
Have fun and enjoy!
Downloads
ROM / Kernel
Hashes
Recommended firmware
Last and latest Oreo firmware for our Mi 5:
8.11.22
ROM installation
Install latest TWRP
Make backups and store them externally
Wipe dalvik, cache, system, vendor, data
When coming from any android version other than Nougat 7.1.2:
Make external backups of your internal storage content
Format data (type "yes" way)
Reboot to recovery to access the data partition correctly again
Flash adequate firmware
No reboot in between the following and the optional steps
Flash ROM
Optionally:
Flash Gapps for 7.1.x arm64. I recommend OpenGapps Pico with additions (1) OR Stock with gapps-config.txt file (2):
(1) Flash Gapps additions (for example these by @Deltadroid)
(2) Check post_#128
Flash ThemeReady GApps package for Nougat arm64 (I don't)
Flash root (Latest Magisk is working fine for me)
After the first boot
Follow the gapps assistant (in case you installed gapps)
Wait 2 - 5 minutes to let everything settle in
Reboot to system
Kernel installation
You'll only wanna install the kernel separately when there's a kernel-only update later than the last ROM version!
Wipe dalvik and cache
Flash the kernel zip-file
Optionally: Re-flash root (if you were rooted before or now wanna be rooted)
GPL
All repos are forked from AOSP-JF-MM or LineageOS
Device tree source code:
https://github.com/PhilSmith31/platform_device_xiaomi_gemini/tree/aosp-7.1.2_r36
Kernel source code:
https://github.com/PhilSmith31/platform_kernel_xiaomi_msm8996/tree/bb
XDA:DevDB Information
AOSP, ROM for the Xiaomi Mi 5
Contributors
Phil_Smith
Source Code: https://github.com/PhilSmith31
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.1.18
Based On: AOSP
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2020-03-20
Changelogs
20.03.2020
March 2020 security updates from LineageOS
Synced Lineage repos
Kernel is up to date with relevant commits to android/common
02.03.2020
Security bulletins up to Februrary 2020 (no more source.android updates coming from here on)
Updated everything in aosp.xml to latest android tag r39
Updated HALs and all externals under CAF to tag LA.UM.5.5.c25-04600-8x96.0
Upstreamed kernel with all changes to android/common up to date
Merged LA.UM.5.5.c25-04600-8x96.0 into qcacld-2.0
Synced Lineage repos
Kicked opencv
Kernel compiled with latest Linaro toolchain 7.5.0
17.09.2019
ROM:
Security updates from August and September 2019
Merged in CAF tag LA.UM.5.5.c25-03100-8x96.0 into externals, hals, and some vendors
Synced system/gatekeeper with LOS
Kernel:
B--B-Kernel-N-[2019-09-17]-[20:17]-Mi5
From now on always also present in kernel_only folder
Cherry-picked all relevant aosp's kernel/common/android-3.18 commits up to date
Merged in security related changes from aosp
Merged CAF tag LA.UM.5.5.c25-03100-8x96.0 into qcacld-2.0
Wrote simple python script to filter out warnings from compile output
Check extract_warnings.py and changes to build_kernel.sh
Vendor/aosp:
Monitor changelog under Dropbox link only
all changelogs
.
FAQ
I'm having general problems with the ROM installation or don't know what steps to perform to move from x to y or to restore or undo z. What shall I do, Dr. Phil?
Dr. Dr. Phil said:
First read the intro and then see whether your problem is covered here:
Standard Installation Types
Still issues? Then feel free to post in this thread!
Click to expand...
Click to collapse
Gcam mod has green lines in portrait mode or even in general
Dr. Dr. Phil said:
Settings -> advanced -> Fix Camera API2 -> support level override
and set it to "Zsl reprocessing"
Click to expand...
Click to collapse
Gcam mod video recording is force closing all the time.
Dr. Dr. Phil said:
This problem is present in Arnova's cam versions > 8, while photo shooting is working fine with the support level override fix above. You could use stock camera for video recording or use Arnova's gcam mod in versions 7.9 till 8.
Click to expand...
Click to collapse
Proximity sensor lets the screen get black while making a phone call
Dr. Dr. Phil said:
Use the recommended firmware (Oreo 8.11.22).
If that doesn't help, here is a fix that I used once successfully when I had the same problem.
Thanks to Mi5 Arsenal!:
flash zcx twrp
make a backup of your persist partition (let's call that x)
store x externally in case the fix shouldn't work or make anything worse (which I don't believe, but still)
download this zip file and place it where x had been stored (replace x with it)
hit restore in twrp, and select the new backup file you just put in place where x was
reboot to system
You can switch to official twrp afterwards without any problem!
Click to expand...
Click to collapse
Xposed isn't working or producing issues, what to do?
Dr. Dr. Phil said:
In my experience, xposed is very powerful, but can produce all kinds of weird and untraceable behaviour.
I don't recommend using it if not completely nessecary, and cannot support it.
Click to expand...
Click to collapse
Reserved
Hi mate... thanks for your dedication on our work!
Inviato dal mio Xiaomi Mi5 utilizzando Tapatalk
This is exactly what I was looking for N Rom with latest patches:laugh: .Ty so much for your work, will try it soon. :laugh:
What is for boot.img?
XxFatiHxX said:
What is for boot.img?
Click to expand...
Click to collapse
Just so you could flash back stock kernel separately.
Nothing you need for the ROM installation.
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
ERRORR2 said:
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
Click to expand...
Click to collapse
You should be able to dirty flash, although I think that a clean flash is advisable.
B-B-kernel should be working, but keep in mind that I am gonna keep updating the stock kernel and the B-B one is getting more and more outdated.
Edit:
This info is outdated!
B--B-kernel is even built into the ROM now!
The ol' but gold rom has waken up from long sleep
This rom is eas or hmp ?
Kyru said:
This rom is eas or hmp ?
Click to expand...
Click to collapse
EAS
Phil_Smith said:
EAS
Click to expand...
Click to collapse
Will it work with latest beta firmware ?
Will try soon
Kyru said:
Will it work with latest beta firmware ?
Click to expand...
Click to collapse
I would suggest Nougat-based firmware, but maybe on Oreo-based everything is working as well - can't say.
You need to try that out (on your own risk).
Thanks very much @Phil_Smith
Finally.. must try this one.. thanks @Phil_Smith
I can't believe this is perfect.
Can you add more status bar customizations?
Does alarm from switched off work with this rom?
Inviato dal mio MI 5 utilizzando Tapatalk

[EOL][SODP][ROM][LineageOS][XZ2, XZ2C, XZ3] LineageOS 17.1 [STABLE][UNofficial]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse
02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1
MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.
The XZ3 Dual file is corrupted. It is only 50MB in size
nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.
MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly
does anyone know how well gcam works compared to stock camera on locked device?
tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.

REBORN KERNEL {11 CAF - 14122021 }

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.
*
*/
​C.A.F 4.14 REBORN KERNEL​
​This Kernel is designed for, security witch general improvement as possible .​​What is features included in this Kernel ?​​driver stable from gram-q-oss debloated ( exept some drivers from mojito-r-oss... )​latest CAF Kernel from LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​latest Techpack audio LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​compiled witch AOSP Clang r433403b (13.0.3).​Merged latest google common android-4.14-stable ( 4.14.258)​*fixed error dts in log​*ttl support for bypass some operator restriction​*schedutil governor debloated​*using pelt instead walt for EAS​*zram lz4 as default / lz4 - lzo updated​*added exfat support from mainline​*latest f2fs from jaegeuk/f2fs-stable​*wireguard drivers added​*enable LTO clang​*security features enabled - CFI clang enforced - selinux enforced by default​*vdso32​*TCP BBR as default , westwood​*Backport TCP cubic​*fixed support to report HVDCP_3P5 adapter​​and probably more check sources for more information about features and change ...​​Compatible Systems with this Kernel​​This kernel is only compatible for Android 11 AOSP CUSTOM ROM.​​kernel version for GSI is only for phh GSI using stock vendor​​DOWNLOAD VERSION AOSP ROM​​DOWNLOAD VERSION TREBLE​This Kernel will receive updates with new CAF tags and new upstream & improvement​​Guide Install :​​Boot into recovery​Flash the Kernel ZIP​wipe dalvik-cache & Reboot to System- enjoy!​​BUG : kernel tested from curtana EEA no bug found actually . ​ -for report bug kernel only (issue rom, firmware issue ,mod flashed ex will be hardly ignored ) ​ -give dmesg/logcat to me and descript issue .​​Thanks for :​​Xiaomi kernel sources​Code Aurora forum for caf 4.14 release​all other contributors no mentionned in sources​​XDAevDB Information​C.A.F REBORN Kernel 4.14 for MI POCO M2 Pro,Redmi Note 9 S/Pro,Redmi Note 9 Pro Max​​Contributors :​@ada12​Source Code​Status: Stable​
14/12/2021
*upstream 4.14.258
*LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0
*various fix kernel by kerneltoast
11/12/2021
rebased kernel to :
latest CAF Kernel from LA.UM.9.1.r1-11400-SMxxx0.0
latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.r1-11400-SMxxx0.0
latest Techpack audio LA.UM.9.1.r1-11400-SMxxx0.0
latest techpack data LA.UM.9.1.r1-11400-SMxxx0.0
Merged latest google common android-4.14-stable ( 4.14.257)
*latest exfat backport of namjaejon
*USB f_fs fix
*usb: fix undefined behavior caused by zero-length array
and more change see sources.
Damages hardware,
{Mod edit}
@ada12 Thread closed. Please advise when the issue with the kernel has been fixed and the thread could be reopened.
Regards
Oswald Boelcke
Senior Moderator
P.S. Thread cleaned from outside-XDA items.
EDIT: @ada12 Thread has been reopened.
BladeRunnerA2C said:
Damages hardware,
{Mod edit}
Click to expand...
Click to collapse
I apologize for issue you have get . I have worked on it and fixed issue before post in xda do not be afraid . kernel is rebased.
regards
ada12 said:
I apologize for issue you have get . I have worked on it and fixed issue before post in xda do not be afraid . kernel is rebased.
regards
Click to expand...
Click to collapse
Well,
I can't risk my phone again on that, so I'll request you to drop the mess you did (which damaged the hardware), find a new way and walk around it,
BladeRunnerA2C said:
Well,
I can't risk my phone again on that, so I'll request you to drop the mess you did (which damaged the hardware), find a new way and walk around it,
Click to expand...
Click to collapse
As I write it's fixed in sources
*And it's software issue it's no damage hardware reflash all firmware in edl resolve error created in fw.
ada12 said:
As I write it's fixed in sources
*And it's software issue it's no damage hardware reflash all firmware in edl resolve error created in fw.
Click to expand...
Click to collapse
Can you send me instruction on how to flash in edl?
Roberto Nigel said:
Can you send me instruction on how to flash in edl?
Click to expand...
Click to collapse
guide for windows . ( solution for linux exist too but no tested in curtana )
You need drivers Qualcomm HS-USB QDLoader 9008 in your computer. { You can find easy by little search in internet }
For enter in edl mod easy method ( I assume for this method you have access to fastboot ) :
reboot to fastboot
* fastboot oem edl
Your device will then will go to black screen only. for verify Your computer reconize your phone now as QDloader 9008 in devices manager , you are in EDL mode.
*Open miflash tools
*Select your fastboot rom for curtana if you have this codename devices ... make sure
Flash it ... Wait ... Done reboot
in TG group reborn kernel has problems. It affects hardware hmmm.
ada12 said:
guide for windows . ( solution for linux exist too but no tested in curtana )
You need drivers Qualcomm HS-USB QDLoader 9008 in your computer. { You can find easy by little search in internet }
For enter in edl mod easy method ( I assume for this method you have access to fastboot ) :
reboot to fastboot
* fastboot oem edl
Your device will then will go to black screen only. for verify Your computer reconize your phone now as QDloader 9008 in devices manager , you are in EDL mode.
*Open miflash tools
*Select your fastboot rom for curtana if you have this codename devices ... make sure
Flash it ... Wait ... Done reboot
Click to expand...
Click to collapse
you cannot use edl mode without xiaomi edl authorized account
tusharind007 said:
you cannot use edl mode without xiaomi edl authorized account
Click to expand...
Click to collapse
Thanks to clarify that I have missed that .
I have 2018 account witch full authorization since it's worked here...
Flashing engeener firmware do a full clean flash too from fastboot .
About firehose patched it's always possible to generate it . Until now I have no worked on it
nice thankyou
I flashed this version of the kernel over your past 4.14.244 and after flashing a constant reboot and had to roll back to 4.14.244 why does this version 4.14.245 not work for me?
Nice
Information about Android 12
kernel have caf tag android 11 [LA.UM.9.1].
Actually caf have no released Android 12 [ LA.UM.10 ]
But Until now no issue is reported in custom rom android 12 using LA.UM.9.1 kernel,flash is safe.

Categories

Resources