Database Develop

[TWRP][INFINIX][3.0.2-0] TWRP for Infinix Hot-2

Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official. Officially supported device get automatic builds which are made available at dl.twrp.me/<device_codename> at each major release. Thank you.
Download : My Website
XDA:DevDB Information
TWRP for HOT 2, Tool/Utility for the Infinix HOT 2
Contributors
MSF Jarvis, Nonta72
Version Information
Status: Testing
Created 2016-04-13
Last Updated 2016-04-13

MSF Jarvis said:
Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official.
Click to expand...
Click to collapse
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.

Nonta72 said:
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Click to expand...
Click to collapse
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.

MSF Jarvis said:
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
Click to expand...
Click to collapse
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.

Nonta72 said:
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Click to expand...
Click to collapse
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.

MSF Jarvis said:
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
Click to expand...
Click to collapse
Sure
Let's make it work! :highfive:

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try

MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
In 15 minutes, there will be twrp-3.0.2-2 available there. If you're interested to see what I did to it, check the commits
This one has logcat enabled as well, so you may wanna help me that way. I don't do WhatsApp, so you may want to hop on to #team-redux on http://webchat.freenode.net rather.

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:

MSF Jarvis said:
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
Click to expand...
Click to collapse
Nonta72 said:
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Click to expand...
Click to collapse
Another test build is up : 3.0.2-2

MSF Jarvis said:
Another test build is up : 3.0.2-2
Click to expand...
Click to collapse
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...

Nonta72 said:
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Click to expand...
Click to collapse
Maybe I should, but where's the similarity?

MSF Jarvis said:
Maybe I should, but where's the similarity?
Click to expand...
Click to collapse
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.

Nonta72 said:
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Click to expand...
Click to collapse
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor

Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)

RendyAK said:
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
Click to expand...
Click to collapse
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??

MSF Jarvis said:
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Click to expand...
Click to collapse
Because MT6580 is a recent version of the MT6582. Forget the "2" that became "0" at the end. The MT6580 is even faster than the MT6582 and can match some MT6592 (with 1GB RAM). I saw a 33,000+ antutu on a MT6580 (with 2GB RAM) and overclocked (yes! overclocked, idk how but they said so).
MSF Jarvis said:
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
Click to expand...
Click to collapse
Sir, you're talking about the messed up ramdisk. In fact, there are many builds, the one you have seen have many bugs probably because of the messed up rcs.
The only recovery that works good for me is the one made by Ovatek. I made few commits to my github including the fstab file changes you suggested...

Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia

Nonta72 said:
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Click to expand...
Click to collapse
Actually speaking, the OEM for the MT6582 device went with naming the device 'sprout', which I vehemently oppose, to avoid confusion. The stock boot.img's ramdisk also contains files according to the 'sprout' nomenclature. I took the sprout4 device tree, updated all *.rc's from the stock marshamallow boot.img and added in a bunch of TWRP flags.
One important thing you most probably already know, Infinix Hot 2 uses a standard MTK boot.img header, while the LAVA Pixelv1 uses an AOSP format, so it can be unpacked using standard tools, while yours requires Carliv's kitchen.

[CM-13.0] CyanogenMod 13.0 Development/Disscussion Forum.

@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero

HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
- HostZero
Click to expand...
Click to collapse
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Roger That!

@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Build Fail. ? Hmm I will submit device tree tommrow for infinix

HostZero said:
Build Fail. ? Hmm I will submit device tree tommrow for infinix
Click to expand...
Click to collapse
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Great!

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Click to expand...
Click to collapse
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?

RendyAK said:
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
Click to expand...
Click to collapse
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
Click to expand...
Click to collapse
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.

Nonta72 said:
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Click to expand...
Click to collapse
Hmm anyways I have pushed the cm-13.0 device tree too I have upstremed as many files as possible.
https://github.com/d5110-devs

MSF Jarvis said:
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Click to expand...
Click to collapse
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.

RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
MSF Jarvis Seems to be compiling and i have ubuntu but.. my package is done! as tree and vendor are ready try to compile.
Here by OFFICIAL TWRP:
https://dl.twrp.me/d5110

RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Click to expand...
Click to collapse
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?

RendyAK said:
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
Click to expand...
Click to collapse
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
OMG! You guys could provide 3.18, I have used the 3.10 which has come with STOCK 6.0 if you guys can provide MSF will update it!
- HostZero

I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.

HostZero said:
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
Click to expand...
Click to collapse
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs

MSF Jarvis said:
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
WTF! I should do again. C'mon man... I ll do later mostly not now. I will send you tree.zip better you can push it. Because my push is failing.

Anyone else trying to build CyanogenMod 14 ?

I'm working on CM14, after a lot of go through I finally zipped it.
but its not booting up.
I used following Resources
Device Tree - It needs a lot of modifications.
Kernel
Vendor Files
MSM 8996 HALs from CM14 are giving Errors, so I used HALs from OMNI
EngMod: Logcat

Bump!
No one?

WhyOrean said:
Bump!
No one?
Click to expand...
Click to collapse
Unfortunately i cant help but i bump this thread
Thanks for your effortand hope someone helps.

Try port rom 7.0 from one plus 3 with file of miui n leak

Update: Got it booting :highfive:
But it seems like its display needs to be calibrated.
It shuts down after a giving a quick glance.
This time I used Precompiled Binaries from TheMuppets
Also Hardware/qcom/display-caf and Hardware/qcom/media-caf throw errors.
So I used ones from CM13 Branch.
-> Syncing CM14.1, seems like CM14 is abandoned.

WhyOrean said:
Update: Got it booting :highfive:
But it seems like its display needs to be calibrated.
It shuts down after a giving a quick glance.
This time I used Precompiled Binaries from TheMuppets
Also Hardware/qcom/display-caf and Hardware/qcom/media-caf throw errors.
So I used ones from CM13 Branch.
-> Syncing CM14.1, seems like CM14 is abandoned.
Click to expand...
Click to collapse
good job man! :good:

Whoa, that would be great, please keep us informed!

Question Any dev working on TWRP?

If not, anyone can make a bount?

matheus_sc said:
If not, anyone can make a bount?
Click to expand...
Click to collapse
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.

pittrich said:
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
Click to expand...
Click to collapse
I know i use xiaomi eu already. Only update is pain to ass

wait for it

Rumour has it some chinese dev is working on it

Any news?

matheus_sc said:
Any news?
Click to expand...
Click to collapse
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.

... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?

raupe said:
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
Click to expand...
Click to collapse
This?
Xiaomi Mi 11 kernel source code is out, the device is codenamed "venus" - Gizmochina
Yesterday, Xiaomi announced Mi 11 as the world’s first smartphone powered by Qualcomm Snapdragon 888. The handset already went for pre-order soon after the launch and is set to go on sale for the first time on January 1. Ahead of its sale, the company has even released this device’s kernel...
www.gizmochina.com

I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.

Danacy said:
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Click to expand...
Click to collapse
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.

[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com

mslezak said:
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
Click to expand...
Click to collapse

*justintime* said:
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
Click to expand...
Click to collapse
Yeah Mauronofrio is out, too much work for no return. He was pretty much the last standing open-source TWRP dev out there for tons of devices. The ones from China never get source released... Which would mean that someone would have to pickup the TWRP project and re-engineer it to fit the new GKI 1.0 then 2.0 platforms that run off that ACK. That's a lot of work. I'm talking about keeping the TWRP project open-source. It would very nice if Google stepped in since they are experts on the new format, but no such luck.

mslezak said:
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
Click to expand...
Click to collapse
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?

Danacy said:
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Click to expand...
Click to collapse
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.

The new Xiaomi.eu weekly includes TWRP for Venus (Mi11) as well as Star (Mi 11 Lite 5G, Mi 11 Pro, Mi 11 Ultra, MIX FOLD) (it's a bootable TWRP, but persists after installation). Seems last week's has added Alioth (Mi 10S, Redmi K40). So I would expect a TWRP for Haydn to show up soon in the weekly Xiaomi.eu releases. Seems they forgot the haydn doesn't have TWRP yet so you can't actually install it! Tried the updater app no go, it can't boot to recovery because they don't have one yet, even though on Xiaomi.eu they say it's available, can't find it anywhere.
BTW the only TWRPs I can actually find are for Venus and Star.
haydn TWRP is not working: https://androidfilehost.com/?fid=14943124697586336730 remember: fastboot boot twrp-3.5.1-haydn.img ... although I tried everything, this TWRP just doesn't work - you boot right into the system after the fastboot boot step. Tried everything I can think of, always boots to system. Guess it's still a waiting game...

mslezak said:
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
Click to expand...
Click to collapse
Just one more question since this has been bothering me; what would be needed from Xiaomi? Instructions on how to build the kernel? Have they ever done this before about something like this? Like, is it a reasonable thing to ask them to release instructions? I know some people working there, I could forward the request.

Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com

mslezak said:
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
OK, I see. Thank you for your reply. I am going to see how far I can get this. Tnx again!

General Kernel source finally released

It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.

NeoPreacher said:
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
Click to expand...
Click to collapse
Finally!!!

Let's gooooooooooo!!!!!!!!!

It only took them a year and three months to release it.
Oh god...

NeoSDAP said:
It only took them a year and three months to release it.
Oh god...
Click to expand...
Click to collapse
lmao

Snapdragon_Mid_2020.SPF.1.0.1R_r00024.0
lol it makes even more sad.

Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!

Zylam Marex said:
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Click to expand...
Click to collapse
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11

nice. they can now close 1k issues regarding spes kernel. hahaha

pulsar said:
nice. they can now close 1k issues regarding spes kernel. hahaha
Click to expand...
Click to collapse
There are some people fixing the issues with source already!

NeoPreacher said:
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
Click to expand...
Click to collapse
Oh wow really, tape2wake works great in PA? I have tried almost all roms but PA. Thank you for letting me know, a shame the Kernel is missing drivers and such. I wonder why Xiaomi is trying to make sure the Note 11 is never developed for, it's such a good phone with a custom rom.

BerserkSlayer said:
There are some people fixing the issues with source already!
Click to expand...
Click to collapse
Haha I think Pulsar was referring to Xiaomi's github page where there would be like 10 posts a day asking for Spes kernel

tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?

aureljared said:
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
Click to expand...
Click to collapse
yes

Much easier to compile this kernel using Clang rather than GCC. Still getting used to it, it's been a good while since my last kernel compile, haha.
Does anyone know how to build a new boot image by hand? I have a working boot.img for PixelExperience and I'd like to replace the kernel with one that I built for testing, but I'm not sure if I should still use mkbootimg like with older Android devices as this is the first time I'll be dealing with a device that uses dtb/dtbo files. Any insights would be welcome.
aureljared said:
EDIT: board_id.h is present in the same directory, not in include/.
Click to expand...
Click to collapse

Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?

SAM209 said:
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
Click to expand...
Click to collapse
For one, it is theoretically easier to keep the device up to date without having to wait for Xiaomi's updates. Some changes that come with Android's monthly security patches are made to the kernel, for example, and having the kernel source code means we can apply those patches faster than if we were to wait for updated kernel builds from Xiaomi.
Some ROMs like LineageOS also require kernels to be built from source (i.e., not prebuilt) for a device to be granted official status.

Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance

jasmin811 said:
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
Click to expand...
Click to collapse
There's nothing to flash here. Only the link to the kernel source. There's still some work to do for a flashable kernel (compiling eg). Also there are drivers missing in the source it seems. What you tried was flashing the uncompiled kernel source package i guess and that.. doesn't work

Oh ok,I though it was finished already.