Related
Optimized CyanogenMod 12 Android 5.0.2 Lollipop for the Redmi Note 4G(QCOM) brought to you by haoyangw
NOTE: This is for the QCOM variant of the Redmi Note, otherwise known as Redmi Note 4G, and NOT the MTK variant of the Redmi Note. In short, this ROM will NOT work on the MTK variant of Redmi Note 4G
NOTE: GApps is NOT provided, use any GApps package you can find. I would recommend Open GApps for Lollipop(link below).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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.
*
*/
Version Number explanation is in the #2 post, changelog and device tree branches for my github repositories explanation is listed in the #3 post
Comment your reviews below or even better, PM me as I won't be regularly monitoring this thread. Thanks again! You will be listed in the credits too
Downloads
ROMs
All ScarletRice builds and addons(AndroidFileHost)
All ScarletRice builds and addons(BasketBuild)
ScarletRice selected builds and addons(XDA)
I don't have the time to link specific builds everytime there is a new one anymore, so unfortunately you all have to go into XDA downloads or AndroidFileHost folder and download the latest one. So sorry!
Recoveries(compiled by me )
CWM, Philz touch and twrp recoveries(AndroidFIleHost)
Addons(includes my custom kernels So keep an eye on it)
Addons(AndroidFileHost)
Addons(BasketBuild)
XDA Downloads(Addons and ROMs)
Older downloads:
ScarletRice Beta 0.1
ScarletRice Alpha 0.02: https://mega.co.nz/#!40cXxKQL!Dd-pk41oJOPJbhLILLGnS9yAE09ly6nKIIfgRzLCpak
ScarletRice Beta 0.1 AndroidFileHost mirror
ScarletRice Alpha 0.01: https://mega.co.nz/#!EgN1lIxY!n7f-o9bujoh6eAu0H8iuaiiGrQ1fG3OCxYoodAyuLSA
The battery life so far on this ROM is amazing! It doesn't face any kind of drain issues so far, except maybe for the infamous Google Play Services wakelocks. To quote:
Swordsman0815 said:
Battery life seems to be amazing... I am off the charger for over 12hrs and still have around 46% of charge left
Click to expand...
Click to collapse
Well good/bad battery life is actually really subjective, some people might have higher standards due to their past experience etc so it all depends! Try it out yourself and see
Not working:
Cast screen/Screen mirroring
FM Radio
Compass
Back Camera and front camera video Fixed now
Buggy power detection Fixed
Flashing red borders(chrome only) Fixed
Working:
Back and Front camera(video + photo)(wipe dalvik if doesn't work)
Wifi
Headphones
Touch
Auto brightness
Gyroscope
Alarms
Location
Double tap 2 wake(built into ROM zip's kernel and my custom kernels) Removed due to bugs
Anything else
Installation
Download the ROM from the link above
Download GApps package for Lollipop(Recommended: OpenGapps, for 4.4+ and all architectures)
Download any addons/custom kernels from links above or anywhere else
Put the zip files on your SDCard
Reboot in Recovery(choose one of the 3 above if you wish )
Wipe Data / Factory Reset(ONLY IF you are coming from another ROM/upgrading to beta 0.2.x to get working camera)
Recommended: Wipe dalvik-cache
Select "Install zip from SDCard"
Choose CM12 zip file
Select "Install zip from SDCard"
Choose GApps zip file
Optional: Select "Install zip from SDCard"
Optional: Choose addon/kernel zip
Reboot system
Reporting bugs
If you have found a bug, make sure you fill up a form here: Google Form: Bug reporting This allows me to easily track all bugs reported without scanning the whole thread. Do make SURE that you fill in a VERY detailed description! And don't forget logs! For a tutorial on how to get logs, here you go! Log tutorial Of course, feel free to still report bugs here as I will be monitoring this thread But you MUST fill up a form, reporting on XDA is optional
Sources
Manifest
For those who would like a shortcut to sync all the neccessary repos to build stable cm12, just download/copy the contents of this file into .repo/local_manifest: Local manifest xml and the next time you repo sync everything will be there Then just 'lunch cm_dior-userdebug' and 'make -j4 otapackage'
Manually
I've finally given up making my own trees and fixing the annoying bugs in Xiaomi's kernel sources, so here are all the working tree/sources brought to you by our awesome devs! I take no credit for this! GO AND THANK THEM!
Edit: I've made some minor updates and fixes to the trees, but still credit goes to them!
Updated trees(updated by me but originally created by the following devs)
Device tree
Kernel source
Vendor tree(a.k.a. prebuilt/proprietary blobs tree)
Original trees:
@Silesh.Nair's device tree
@Silesh.Nair's vendor tree
@audahadi's kernel source
@stane1983's kernel source
I've uploaded the device tree I used to compile twrp to my device tree above, the branch name is 'twrp'. It's based on syhost's outdated twrp device tree, with problematic flags removed to fix bugs and also translated back into english, so there you go!
NOTE: Currently this device tree is ONLY for compiling CM12, you can face all kinds of build errors if you compile CM11 with it. For example, you will not be able to compile sepolicy in the device tree. You have been warned. Have fun building
Credits
CyanogenMod
XDA
syhost(for his twrp device tree)
Stane1983(for his first working trees)
Silesh.Nair(for his updated trees)
sm_94(for his suggestions on fixes)
And everyone else who contributed logcats and findings and worked hard for the better of all Note 4G users. Thanks!
XDA:DevDB Information
ScarletRice, ROM for the Xiaomi Redmi Note
Contributors
haoyangw
Silesh.Nair
sm_94
stane1983
sadlmadl(Contributed best and most logs and reports)
Swordsman0815(Contribute working/not working reports and logs )
@suhasgta(contributed logs, suggestions and reports )
And all others who contributed logs and reports! Thanks A LOT!
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-03-17
Last Updated 2015-11-29
Version numbers
Version Number explanation
There will be 4 naming conventions for builds, namely Alpha, Beta, Release Candidate and Stable.
Alpha - Build is NOT tested and may not boot
Beta - Build has been tested and boots up, but there are many device-related issues and bugs
Release Candidate, or RC - Build has been tested and device-related issues and most bugs are fixed
Stable - No more than 3 minor bugs and no performance or battery drain issues(caused by ROM on my side)
Changelog + Github Repos' Branches
Changelog:
1.0
Device:
Fixed front and back camera(photo+video) as well as video playback
ROM:
Optimized with O3 and graphite
Enabled optimizing compiler for ART
Kernel:
Added more cpu governors(total 23)
Added gamma control
Added faux sound control
Added alucard and intelli hotplug
Compiled with O2
Maybe more(can't remember)
0.2.4
Device:
Merged changes from sileshn
Fixed some more webview problems(that were not caused by the previous absence of webview completely)
Added FM blobs, FM radio should work properly now (also means you'll need my new local manifest to sync qcom's fm stuff)
Tweaked media configs, hopefully improves some stuff(but playing youtube videos and the like still not working )
0.2.3.1
ROM:
Fixed superuser
Device:
Fixed google play store crashes
Tweaked button brightness, hopefully it isn't too bright nor dim
Old builds' changelogs:
0.2.3
ROM:
Compiled with user instead of eng, should result in increased performance!
Fixed performance issues! Now it's faster than syhost's cm12.1! You know what that means? if we build for cm12.1, then bam, performance will be faster than a rocket! And did I mention Justarchi optimizations and graphite flags?
Many vulnerability fixes like the new Serialization vulnerability
Device:
Bright button lights should now be fixed No light at all Sorry!
Location should be working properly now, without relying on Xiaomi's partners like Qualcomm
Fixed annoying flashing red borders ONCE AND FOR ALL!
0.2.2
Clean install(i.e. with factory reset required for working front camera)
ROM:
Fix Gapps problems(e.g. Play store and google keyboard crashes) by removing system jar compression tweak
Improved performance a little
0.2.1
ROM:
Fix prebuilt WebView that caused browser crashes
Add some missing blobs to increase performance
0.2.0
ROM:
Integrate home button fix
Upstream fixes(most notably stagefright vulnerability fix)
Use prebuilt WebView
System jars 0 compression(store only), but causes problems
Add Open Camera as system app
0.1
ROM:
Finally boots
Fix front camera
Device:
Use Silesh.Nair's device tree to fix problems and make ROM boot
Custom kernel:
V1.2.4:
Updated intelliactive and intellidemand to faux's latest sources, no longer using some outdated files that I got because of laziness So intelliactive is finally working properly(no reboot), and also better performance/battery etc
Added intelli hotplug driver, do check it out!
Updated simple and simpleondemand gpu governors, but they still don't work So do AVOID them!
V1:
Add intelliactive and smartmax governors
Add SIO and ZEN I/O schedulers
Experimental fix for back camera
Github Repository Branch Explanations:
Kernel source repo
cm-12.0: stock cm12 kernel without extra governors and I/O schedulers
cm-12.0-custom: CM12 custom kernel with extra governors and I/O schedulers
stock: Original kernel source from Xiaomi with only fixes for compilation errors
cm-12.0-wip: latest fixes/additions for cm12 that may not work/compile successfully
Upcoming(when it appears on the kernel source repo, cm12.1 is coming ):
cm-12.1: CM12.1 custom kernel with extra governors and I/O schedulers
cm-12.1-custom: stock cm12.1 kernel without extra governors and I/O schedulers
wip-cm12.1: latest fixes/additions for cm12.1 that may not work/compile successfully
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
I wouldn't mind being a tester! I'm installing now and I'll see how it works.
fix
what about camera. fixed or not yet
It's stuck on the MI boot screen.
Finaly
thanks haoyangw for this thread. I would to participate but I just a noob and don't have skill about devs . I just follow and subscribe this thread, hope you can fix any problem about this devices. :good:
i can also help testing,i have min knowledge about what a rom is and logcat.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Good to see someone is working on CM12 for our phone. I tried CM12 syhost version and it's awesome but camera doesn't work and I need it. If you manage to get camera to work that would be awesome.
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
What is the point of this thread when the rom doesn't even boot
i think,
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
I didn't know but i hv subscribe
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
The point is to encourage someone to work on device. Right now it gathers little to no interest at all.
shyampareek said:
What is the point of this thread when the ROM doesn't even boot
Click to expand...
Click to collapse
Point is to give support to developer, or this thread will die. I think u shouldn't be on this forum, so ungrateful
haoyangw said:
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Click to expand...
Click to collapse
Sure, maybe this weekend kind of busy this workdays.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Nemado said:
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
Click to expand...
Click to collapse
Yeah I thought of that, I copied some bits from the desire 816 device tree for Redmi Note 4G. I've tried building recovery with my sources and device tree and the recovery works perfectly, so I think it must be something in the ROM that is the problem. I'll need a logcat for tracking the malfunctioning part.
robreyes07 said:
Sure, maybe this weekend kind of busy this workdays.
Click to expand...
Click to collapse
Thanks a lot! Hope I can get this ROM working soon, then our beloved device will get Lollipop sweetness.
Have you tried to compile kernel that xiaomi relased for our device?
Hello guys,
i am looking for some custom rom for my x910 leeco.
Could i use maybe lineage os, z2 for that?
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
ThE_MarD said:
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
Click to expand...
Click to collapse
any update ?
Cateye said:
any update ?
Click to expand...
Click to collapse
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Keep working please. We count on you.
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
xaakx said:
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
Click to expand...
Click to collapse
Heyyo, can you please get me logcat from the start of the device booting? I've tried importing all 18 max_plus dts/dtsi files I saw in the kernel but that still didn't get it to boot.
https://github.com/LineageOsMaxPlus...mmit/7eb4dbf827bba4e05de2a802b6fc2b05741b04b9
Here's so far everything I've tried to do
https://github.com/LineageOsMaxPlus
I've been thinking of upgrading my nearly 2 year old x910 since I've been stuck on this hacked chinese rom version of android 6.0.1 (Kernel version 3.18.20 from April 29, 2016). Apps are starting to crash or drain battery, etc
Is there anything I can do? I know X910 was some sort of engineering sample run and never mass sold. I was lucky enough to find one on aliexpress for about $280 2 years ago. Been a great phone but Android 6 is killin me now.
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
ThE_MarD said:
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
Click to expand...
Click to collapse
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
xaakx said:
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
Click to expand...
Click to collapse
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
https://youtu.be/TYfFmDjOQnk
Hello sir
A noob here with x910
Please tell us that should we hope for a stable custom rom on this device like we have on le max 2?
Heyyo @King Ibsd , I am still trying to work on it! :good:
I do have unified builds with X2 working, so that part is good to go! Just need to resolve this panel issue hmm...
I forgot to mention this earlier... But if you're really interested in trying experimental max_plus unified with X2 builds? The last few builds I've posted in the X2 thread are unified with max_plus... But be warned, it has serious video lag as noted in that YouTube link up above.
There is a chance your max_plus has a blank devinfo block which isn't good as we check that for many things on custom ROMs.
If yours is blank? Please flash this via TWRP to correct it to max_plus.
https://drive.google.com/file/d/0B7RnSWm3LBorZ1NzNmtrcmNlV1ZzZ3U0WFdWQnF4bXB0Sm80/view?usp=drivesdk
Hmm, I think the signed graphics firmware I was given for max_plus is REALLY out of date and could be the reason for the video lag...
Can someone here please link me the latest version of EUI ROM that works for max_plus?
ThE_MarD said:
Can someone here please link me the latest version of EUI ROM that works for max_plus?
Click to expand...
Click to collapse
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Palm Trees said:
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Click to expand...
Click to collapse
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
ThE_MarD said:
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
Click to expand...
Click to collapse
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Palm Trees said:
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Click to expand...
Click to collapse
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
ThE_MarD said:
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
Click to expand...
Click to collapse
I collected the x900(乐视_X900)/x900+ (乐视_X900加)/Le Max fastboot images (all models are msm8994 "Snapdragon 810"). So I do believe LeEco was lazy when they created the msm8996 phones. As far as I can tell, LeEco was the first company (or one of the first) to use msm8996. So they might have said "Yeah well, let's move from msm8994 to msm8996 without changing stuff" in the NON-HLOS.bin.
If you want to compare the NON-HLOS.bin from the msm8994 phones with the other NON-HLOS.bin files from the msm8996 phones here are the links and descriptions:
1523500103_MAX1_X900 CN FN CEXCNFN5902803208S 5.9.028S //latest fw release (not fastboot images)
Source: http://bug.letv.com/cn/download/phone/32
Direct DL-link: http://ota.scloud.lfengmobile.com/ota/1523500103_MAX1_X900-CN-FN-CEXCNFN5902803208S-5.9.028S.zip
ro.letv.release.version=5.9.028S
ro.product.letv_model=Letv X900+
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-01-01
ro.build.date=Tue Mar 20 20:00:44 CST 2018
ro.product.model=X900
ro.product.brand=Letv
ro.product.name=max1
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.date=Tue Mar 20 20:31:41 CST 2018
ro.bootimage.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/test-keys
Geekbuying posted the Indian firmware. The .zip file and general description are incorrectly tagged. Nevertheless, it is in fact the Indian Le Max firmware for msm8994 based on Android L 5.0.2.
LETV X900 LE MAX PRO Snapdragon 820 Quad Core Android 5.1 Smartphone Firmware
Should be tagged something like this LeTV X900 5.5.014S 5.0.2
Source: http://blog.geekbuying.com/2017/08/...ore-android-5-1-smartphone-firmware-20170818/
DL-link:http://www.mediafire.com/file/h8276...oid+5.1+Smartphone+Firmware+-5.5.014S-5.0.zip (Password: geekbuying.com)
# begin build properties
ro.letv.product.info=Max1_r1148.5-5.0.2-userdebug_CHN-OPEN-Dev
ro.letv.release.branch=x1_stable_011_20160125
ro.letv.release.version=5.5.014S
ro.build.date=Sun May 22 03:29:13 CST 2016
ro.product.model=Le Max
ro.product.name=LeMax_WW
ro.product.device=max1_in
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_WW/max1_in:5.0.2/CHXOSOP5501405221S/154:user/release-keys
The Chinese firmware below is pretty much comparable except for a few differences in system.img (some apps are included/excluded). Unpacking the boot.img did show comparable ramdisks.
乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
Source:http://url88.cn/Jk9eBy
Direct DL-link:http://rom.url88.cn/{3705256}_乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
ro.letv.release.version=5.5.009S
ro.product.model=X900+
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Source:http://url88.cn/1a9Cpmr
Direct DL-link:http://rom.url88.cn/{3704883}_乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ro.letv.release.version=5.5.009S
ro.product.model=X900
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ThE_MarD said:
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
Video lag for the twrp is completely gone after adding few additional lines that were missing from maxplus device trees as compared to similar dsi panels of Max 2 in your test rom. Following are the additional lines for my device panel mdss_dsi_sharp_qhd_dualdsi_cmd from MSM 8996 v3 + PMI8994 LE_X2_NA-DVT1.1 which looks similar to my device tree dvt3.
qcom,mdss-mdp-transfer-time-us = <0x2710>;
qcom,ulps-enabled;
qcom,config-select = <0x2c>;
config0 {
qcom,split-mode = "pingpong-split";
linux,phandle = <0x2c>;
phandle = <0x2c>;
I couldnt add last two lines for phandle nodes as they are found else where as well. The most important line that fixed the lag of twrp is qcom,config-select = <0x2c> which looks specific to my device. I tried to boot the rom after flashing modified boot without those last two lines for phandle nodes, but the phone screen goes blank while booting. Interestingly, config select and phandle node values are same for pingpong split modes and they are in the range of 0x2a to 0x2f . Once you incorporate these lines with the appropriate pingpong split mode, hopefully the rom should work without any lag as well. Looking forward to next build soon....
Click to expand...
Click to collapse
Linux Kernel 4.9 for Moto G5
As you guys already know, our Moto G5 has an ancient linux kernel (3.18.x) which is now EOL (end of life) from support from actual Linux Foundation. It's pretty much stuck there with no probable updates to it (can use the android 3.18 for updates, but I think that's pretty much soon to be deprecated).
I have been working on this kernel since the past one year and finally managed to boot it on our Cedric!
WARNING: THIS KERNEL IS STILL ALPHA AND MOST OF THE BUGS HAVE STILL NOT BEEN FIXED.
I just wanted to share this kernel with the community!
What works:
Boots
Display
Touch
Storage
Charger
Battery Indication
Bugs:
Pretty much every basic thing
RIL (Calls, mobile data, etc.)
Vibrations (Weird and too strong)
Camera
Flashlight
Only Oreo boots so far.
Want to try for yourself?
Click Here to download link LineageOS 15.1 with Linux Kernel 4.9
Huge Thanks to @wiktorek140 for helping me out with bugs and congratulations to him for booting 4.9 on Montana
Leave a thanks if you like my work!
Buy me a Cup of Coffee or Beer here
XDA:DevDB Information
Linux Kernel 4.9, Kernel for the Moto G5
Contributors
m_vaisakh, wiktorek140
Source Code: [url]https://github.com/mvaisakh/msm-4.9[/URL]
Kernel Special Features: Linux Kernel 4.9.x
Version Information
Status: Alpha
Created 2020-03-30
Last Updated 2020-03-30
Reserved
You can find screenshots here:
https://m.imgur.com/a/OWEhM3b
NOTE: The screenshots are from 2 different builds and hence the difference in kernel version.
Cheers!
Update:
I've been working to fix display and audio on for us.
You can check the progress in my kernel repository. I hope to fix it soon!
Nice! Simply nice. This will hopefully get more attention :good:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
m_vaisakh said:
Update:
Indian variant finally boots now!!
Thanks to Neosight from Mido community for the fix!
It was because of the bootloader not accept the arm IOMMU of cedric (atleast in indian variant). Instead the kernel sent a full aarch64 (or arm64) iommu tz cb, which wasn't getting a secure pass from bootloader through qseecom interface, which apparently states that motorola still uses older (nougat) bootloader in XT1677 (or the Indian variant).
Click to expand...
Click to collapse
Ig edit the op then :angel:
nift4 said:
Ig edit the op then :angel:
Click to expand...
Click to collapse
Updated OP.
m_vaisakh said:
Updated OP.
Click to expand...
Click to collapse
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
devvikram said:
bro how did u update from v3.18 to v4.9 ? Pls I wanna know where can I study about this?
Click to expand...
Click to collapse
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
m_vaisakh said:
CAF had added support for msm8937 for 4.9 with Android Oreo, I just used their base and added moto g5 specific changes. It may sound easy, but it's not.
Click to expand...
Click to collapse
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
devvikram said:
where to study on this??I want to do with my Snapdragon 625 . It's v3.18 which I have to upgrade to v 4.9
Click to expand...
Click to collapse
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
m_vaisakh said:
There's no specific documentation for this. It was all trial and error. Have you read the OP? I've clearly stated it took me 1 year to get it to work.
To start, you should know your way around linux kernel and for reference you can use my source and well there are many other devices that were 3.18 and now run 4.9
Click to expand...
Click to collapse
thanks alot
I overtook the development and got a few quite nice results. Current bug list:
Boots -
Bt -
Wifi -
Camera -
Vibration -
Gps -
Audio -
Ril - (no call audio)
Fp -
Light Sensors -
Accelerometer -
Proximity -
Gyro -
Mic -
Usb Tethering -
MTP & ADB -
Headphones -
Offline Charging -
Flashlight -
SD Card -
FM Radio -
Issues:
Rebooting to recovery boots to system.
Random reboots.
(that is on Android 10)
my source is at https://github.com/n4experiments/
and thanks to wiktorek140 and his 4.9 montana port because without him I would never be able to get so far
Z5C is originally deployed with bluetooth 4.1, however it seems that his chip is capable of an upgrade to 4.2 and maybe even to 5.0.
( idk if it is 5.0 upgradable, here are referring to it as it is:
https://community.infineon.com/t5/W...x/Bluetooth-BCM43455-security-mode/m-p/266305 )
Here I found infos on the BT chip type:
GitHub - seemoo-lab/nexmon: The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more
The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more - GitHub - seemoo-lab/nexmon: The C-based Firmware Patching Framewor...
github.com
Here it is broadcom related infos, with an upgrade in 2019:
https://device.report/broadcom/bcm43455
BT 4.2 introduces some security features and a 10x capacity and 2.5x speed increase for data packets, bt 5.0 increases also the range.Here a quick reference:
Bluetooth - Wikipedia
en.wikipedia.org
Are current mod roms upgraded or there are been tries to do do that?
tagging @Berni-0815 as he the main developer of this handset
For that we need the hardware drivers. Without them it's nearly impossible to upgrade this stuff.
Ok.
Has the hardware driver to be device specific ( ie written for z5c, which I think is impossible to find ) or could be taken from another device's blobs, or even from sources like this one?
Cypress Android 10 Release [2021-01-14]
Framework Version cy-imx-android-10.0.0_2.0.0-6 Kernel Verison Linux localhost 5.4.3-00002-ga85b5953f05b #1 SMP PREEMPT Wed Dec 23 07:58:53 CST 2020 aarch64 FMAC Version v5.4.18-gamera-android-2-0-gde98449dbb46 Release Date 2021.01.22 Description Cypress Android release for the broad market...
community.infineon.com
tagging also @TRKARTAL as searching on github I've seen that in the past has worked to patch this firmware
I for myself have given up to fiddle around with hardware related drivers or patching them.
Kirisakura-Kernel for the Asus Zenfone 9
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila", while the Zenfone 8 bore the title "Sake".
This year seems to make a change however. The Zenfone 9´s internal codename is "DaVinci".
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
As far as we, @tbalden and me, are aware and as far as we know this project, alongside CleanSlate kernel for the Zenfone 9, marks the first release of a source compiled custom QGKI 2.0 kernel as a standalone flashable zip and project here on XDA.
The introduction of GKI and QCOMs adaptation QGKI means unfortunately that building a monolithic kernel becomes harder and harder. This results in the "kernel" itself no longer just sitting in one partition or the zImage, but it´s spread across different partitions (no longer being monolithic) now. Since there´s no requirment to keep monolithic builds working as in the past, it´s no longer possible to compile the source as is (without applying major rewrites, tricks or hacks) in the monolithic fashion on 5.10 kernels. The same was true for the Pixel 6/Pro.
That means the "kernel" project you´re seeing here needs to be compiled in a build environment to achieve the GKI/QGKI way. Since only Google releases the full build environment alongside the kernel sources itself in a proper fashion with git history, it became very complicated and seemingly impossible to do this on the Zenfone 9 at first glance. A big thanks at this place to Asus. From all the sources of SD8 Gen 1 QGKI devices published, the Asus Source is the most complete. A big thanks to Asus for publishing the sources on time and complete! Also for listening to us if the source is not complete and something is missing.
With excellent teamwork and a lot of hardwork, @tbalden and me managed to compile the Zenfone 9 kernel in QGKI 2.0 fashion after a lot of failed attempts and misery. It´s been a pleasure to work with him over the years here on XDA.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
If that got your curious, I welcome you to continue reading if you´re still interested!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. Starting with 5.4 kernel ( SD 888 ) CFI and SCS were enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
I put the explanations and links in hide tags here.
Spoiler: Documentation Control-Flow-Integrity (CFI) / Shadow Call Stacj (SCS)
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.
Another security feature is Shadow Call Stack (SCS).
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above got you curious, have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Read more about the Release-Model following this link.
This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
Starting with the Initial Message , the following reply and a good summarizing statement.
Quick explanation of QCOM-Upstream. CLO-git is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 8+ Gen1 that´s built into the different SKUs of the Zenfone 9.
The kernel-bases available on QCOMs git, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 13 and intended to be used on the latest Asus Stock-Firmware
- compiled with Clang 16.0.2 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 5.10.181
- upstreamed QCOM base for the Snapdragon SD8+ Gen1 (qcoms internal codename "cape")
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- include important fixes/improvements from kernel/common
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- implement ramoops for easier logs in case of kernel panics
- implement LRNG (see arter kernel OP for more info )
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or Kernel Flasher (free open source solution, get it here)
- Anykernel zip is based on the Anykernel3 release from @osm0sis
EAS related features:
- Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
- EAS implementation patched up to latest CAF state
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
- vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.10 default, keep for documentation)
- improve suspend/resume from audio driver (caf-upstream for audio-kernel)
- enable suspend_skip_sync to save power during suspend/resume
- speed up face unlock
- reduce camera launch time
GPU related features:
- GPU driver updated to latest CAF-State
File System related features:
- f2fs improvements
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 9 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.
- add option to force 240hz touch sample rate
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- includes new bbr
- Enable support for TTL spoofing
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
- Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
- enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)
Other features:
- clean up asus drivers and fix a few warnings in kernel log
- enlarge dmesg size to ease debugging
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img, vendor_boot.img, vendor_dlkm.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware via payload extractor)
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 9 receives an OTA update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
Always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip in your favorite kernel app (I personally use Kernel Flasher by @capntrips as it´s free OSS) or TWRP once available.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder:
AFH is currently down. Please check release posts for attached files.
https://www.androidfilehost.com/?w=files&flid=335947
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87544785
1.1.0 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87641829
1.1.3 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87761015
Android 13
2.0.0
[Kernel][09.12.2022][Android 13] Kirisakura 2.0.0_T for Asus Zenfone 9 aka "DaVinci"
Kirisakura-Kernel for the Asus Zenfone 9 Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 9 aka DaVinci. The Zenfone line-up internal codenames were traditionally derived from alcoholic drinks. Two years ago...
forum.xda-developers.com
2.0.6 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-87945357
2.0.12 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88194923
2.0.18 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88332217
2.0.19 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88360955
2.0.21 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88384057
2.0.24 https://forum.xda-developers.com/t/...s-zenfone-9-aka-davinci.4489055/post-88600875
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Asus for the development device, giving me the opportunity to create this project! This device is absolutely stunning!
@osm0sis for all his work, including the ak3 installer!
@capntrips for his relentless work on several projects, including kernel flasher!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_DaVinci_AI2202/
For necessary changes to other repos, besides the main kernel tree please check tbaldens github, we did the bringup together:
tbalden - Repositories
engineer. Started github with kernel for HTCDoubleshot, migrating version in 2011. kernel follows kernel, patching intuitive new features into CleanSlate line. - tbalden
github.com
F.A.Q:
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img from the matching factory image provided on googles download page.
If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.
Flash those images via fastboot/fastbootd and you will be back on stock kernel.
boot.img, dtbo.img and vendor_boot.img are to be flashed in regular fastboot.
vendor_dlkm.img is to be flashed in fastbootd (you can get to this with "fastboot reboot fastboot" when you´re in regular fastboot)
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
taken from pixel 6 soon to be adjusted
AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
this one too
and this one as well
Woohoo! Rock'n'roll! ^__^
Update to 1.1.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Freak07 said:
Update to 1.1.0
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2040.2040.23.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- Linux-Stable upstream bumped to 5.10.146
- merge latest CAF-Upstream
- bump clang to prebuilt 14.0.7 from google
- fixed clang warnings in the process
- other improvements and tweaks please check github
Download:
AFH is currently not working properly. Please check this post for the download. Kernel.zip is attached.
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Click to expand...
Click to collapse
Hello sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Update to 1.1.1
Hey guys and girls,
Here´s the next update. It includes quite a few changes.
It also includes the few kernel changes from the latest firmware 32.2050.2050.29.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.29
- other improvements and tweaks please check github
Download:
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Lossani said:
Hello sir,
How do you compile the original Kernel? Is any of vendor_boot or vendor_dlkm images the same as original stock or both are different? What about DTBO? I'm trying to build kernel for ROG Phone 6 but I thought kernal was still a monolithic file, so I flashed one only and failed to boot. ROG Phone 6 includes a script that apparently compiles everything but I don't which one is DTBO, vendor boot and vendor dlkm. Where and how you compile this kernel and where does the output go? For example I see kernel-platform/msm-kernel as the one you modified? That one is the vendor_boot?
Thank you for your help
And by the way, any plan for Kirisakura for ROG Phone 6?
Click to expand...
Click to collapse
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Freak07 said:
boot.img contains the zImage, vendor_boot contains first stage kernel modules, vendor_dlkm contains second stage kernel modules.
Kernel is no longer monolithic by default. I´m using the build environment to get the relevant images for GKI.
Click to expand...
Click to collapse
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Lossani said:
Do you have any kind of tutorial to follow to pack the kernel like you do in AnyKernel zip?
Thank you
Click to expand...
Click to collapse
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts/methods we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can flash any modified vendor_dlkm.
Be aware, disabling the flags triggers an inevitable wipe.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Freak07 said:
I´m sorry but a step by step tutorial I don´t have the time to type that all down.
Please check tbaldens github for ZF9. We did the "bringup" of the ZF9 GKI environment together.
That here contains the scripts we basically use both.
GitHub - tbalden/android_kernel_asus_zf9_build_env
Contribute to tbalden/android_kernel_asus_zf9_build_env development by creating an account on GitHub.
github.com
Check all the other zf9 repos as well.
We took basically the asus build script inside the ROG 6 source, readjusted it for the ZF9 source, as the build environment for the ROG 6 was more complete than ZF9.
You either need to remove avb from fstab (that lands in vendor_boot) or disable vbmeta flags for verity/verfication before you can modify vendor_dlkm.
Otherwise check the scripts and work yourself through all the repos.
Unfortunately with GKI kernels you need to adjust the ABI. Now it gets complicated. The gki kernel, the zImage is usually compiled, from the common repo, while the qcom specific drivers are built in the msm repo. Since I don´t care about preserving googles abi for the GKI kernel, I compile the zImage from the updated msm repo, as well as the qcom modules.
That means in my build environment common repo is a symlink of msm repo, while I compile with the same script found in ROG 6 source. I think once you start working through the build environment you´ll understand. Tbalden doesn´t need to do that, as his kernel is close to stock with only a few mild changes, so easier to keep abi in check.
Unfortunately at the moment there´s no easy way to compile it.
Click to expand...
Click to collapse
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Lossani said:
Thank you for your reply. I succeded to compile using ROG 6 script but I end up with a vendor_dlkm.img in out/target/platform/taro and in gki folder "dist" outputs Image, vendor_boot.img and another vendor_dlkm.img + dtbo.img but doesn't seem to be the correct size, I guess there's another step missing to compile or I don't know which one of the dlkm is the correct one or if I need another step to make the Image file and vendor_boot.img.
Thank you anyways
Click to expand...
Click to collapse
check the scripts I just sent you. the vendor_dlkm and vendor_boot from the environment don´t work on the device.
The thing is, asus just uses the kernel environment to precompile zImage,all the modules, dtb and dtbo, then transfer those to their complete build environment and those get includes into the images that end up in the firmware. The zImage they´re using on the device is actually not the one compiled in the build environment, but the GKI kernel uploaded by google. That´s why abi is so important. You´re not supposed to flash the ones produced by the build environment.
Check the scripts how repacking both of those works. If everything is right, that will get you to boot.
the zImage you can get from ASUS_AI2202-32.2030.2030.26-kernel-src/kernel_platform/out/msm-waipio-waipio-gki/dist
Update to 1.1.3
Hey guys and girls,
Here´s the next update. Linux-Stable up to 5.10.149, which also fixed the CVEs discussed here and here.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 32.2050.2050.34
- merge latest kernel/common
- linux-stable to 5.10.149
- includes a few fixed CVEs
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Update to 2.0.0
Hey guys and girls,
Here´s the next update with source for A13 stable merged. (not much changes, hence the fast release)
Update to A13 stable before flashing this.
The link to the latest firmware can be found following this link.
More changes in the changelog below:
Changelog:
- included few changes from firmware 33.0804.2060.65
- merge latest kernel/common
- linux-stable to 5.10.157
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
Update to 2.0.6
Hey guys and girls,
Here´s the next update. That´s a bigger one. I´ll explain a few things below in more detail.
The link to the latest firmware can be found following this link.
Monolithic kernel build
Thanks to @arter97 it´s now possible to build the 5.10 qcom kernel now as a monolithic kernel, not needing to build as a GKI style kernel.
To explain it simple: The problem is QCOM/Google are no longer required to test if drivers are loading in the correct order and or test compilation of a monolithic kernel at all.
The gki style kernel has 100s of drivers build as external kernel modules, instead of directly into the zImage.
Having a monolithic build eases development a bit, but won´t directly make an impact to the user.
If you´re interested check my github, it contains the commits. and be sure to drop @arter97 a few thanks somewhere!
Introduction of Lazy RCU
Usually I´m not stating remarks about a change improving battery life notably. But this is one of the few kernel changes that really does make a noticeable difference.
This kernel has the entire(!) RCU subsystem updated to latest linux 6.0 kernel state. This also allowed for Lazy RCU to be merged into the kernel, which should result in power-savings while the device is lightly-loaded or idling (which is basically the case all the time a smartphone isn´t being interacted with (nothing touching the screen and no other workload such as video editing is done).
If you´re interested in details check the slides, which are also linked in the article mentioned/linked above.
A very simplified explanation: RCU functionality can be called 1000s of times a second, batching RCU calls can save power by not calling as often.
Please keep in mind, those are kernel changes and battery life will not be improved magically by huge amounts, but there´s definitely an improvments.
Sony Scheduler Improvements
Import some scheduler changes around Walt from Sony Xperia 1 IV. This improves jitter by a significant amount.
More changes in the changelog below:
Changelog:
- merge latest kernel/common lts branch
- linux-stable to 5.10.160
- merge latest qcom upstream to main branch
- bump clang to latest prebuilt from google 16.0.2
- lazy rcu backported
- scheduler improvements from Sony Xperia 1 IV
- remove wlan rx wakelock as it´s unnecssary
- other improvements and tweaks please check github
Download:
Attached to release post, AFH is currently broken
https://www.androidfilehost.com/?w=files&flid=335947
Instructions can be found in the OP!
But look at this post too
Have fun, enjoy the kernel and your phone.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
luki2411 said:
is there any possibility you could try to make such a kernel for rog 6 ? if you had a tester
Click to expand...
Click to collapse
hi everybody. this is a very voluminous work, but still, if you decide, I am ready to take an active part in testing.
Hi Freak Will you port this kernel to ROG Phone 6 ?