Hello everyone,
I recently got this phone and of course noticed xiaomi didn't release the kernel source.
So I'm planning on trying to build a kernel from source that would work with stock miui (I'm aiming for 13.0.13.0 EU android 11 version at first).
My starting point is the source from CAF: LA.UM.9.15.1.r1-07200-KAMORTA.0. If you think a different source would be better please let me know, but I thought this one came closest).
Now I am looking at the Mi github for devices comparable so I can get some specific xiaomi/component source stuff. Currently looking at Redmi POCO M3 its A10 but should be okay.
I will post a link to github soon.
Just letting you know.
SOURCE: https://github.com/daeiron/spes_kernel
So I now have a compilable source here: https://github.com/daeiron/spes_kernel
I used proton clang to compile.
Okay so here is the first result, this is untested. But if someone wants to test it go ahead. My phone isn't unlocked yet
You could first try flashing test_boot.img to boot partition and see what it does (you should be on 13.0.13.0 stock), if that doesn't work you could try flashing dtbo.img to the dtbo partition.
Please make a backup first! This probably won't work.
This is very interesting.
It's great to see that there is another way to have a kernel source, even if Xiaomi doesn't want to release the official.
I'm in the middle of a move, so I can't test it because I need my phone fully functional, but I should be able to help out in time, especially once the kernel is more stable.
Can someone provide me a full dmesg log and maybe a logcat from just after boot. I could take a look at that while I am waiting for the unlock time of a stupid 7 days.
Does anyone have a schematic diagram for our phone? Im trying to find the UART pins
How the project is doing?
I have some of the drivers, extra functions, device specific stuff ready in the source with some cherry picking and reverse engineering the stock kernel with ghidra, but not (nearly) everything. I was planning to find if there are uart pins on the main board with a logic analyzer as it wouldnt make sense to go forth without testing and getting it booting. Because it isn't booting yet. But Im going on a vacation to mid February so there won't be much progress until then unfortunately. If i remember correctly I still need to do the touchscreen/lcd driver (nt36...& focaltech, bq25.. charge driver, all camera's, all connectivity (this shouldn't be hard) and probably some more stuff. There is some source code out there for some of the things but they are not identical to the reversed source so that will be more tricky.
Something to keep in mind, there is most likely a bug in the wifi or the Bluetooth driver ( perhaps both? ) that causes the device to freeze a bit when both are on and the wifi signal is bad.
My guess is that the wifi driver tries to reconnect way too often and something freezes
this is for redmi note 11?
and what's android version 11,12 or 13? pls
yorux2016t said:
this is for redmi note 11?
and what's android version 11,12 or 13? pls
Click to expand...
Click to collapse
Presumably based on Android 12 kernels. But I believe it works regardless on the version. OP of this post literally is doing God's work
thomas1991_12 said:
Does anyone have a schematic diagram for our phone? Im trying to find the UART pins.
Click to expand...
Click to collapse
I've never seen any schematics for anything and I can't believe they would be helpful.
A PCB layout would be helpful, but I haven't seen that either.
In ye old day a UART might have some level shifters.
Nowadays things are more minimal.
You'll get the raw pins out of the SoC.
You'll probably need a USB UART adapter that can work with 1.8V logic levels.
It would be nice to find the reset line, that's very helpful for hacking.
That way you don't have to wait for 10 second power button pushes.
An oscilloscope on likely test points on the board while booting is the easiest way to find a UART.
My specialty is Android ereaders and I've got a half dozen with permanently installed UART connectors.
I think UART should be your last resort, pretty sure the kernel should be writing to RAM and you can read that.
thomas1991_12 said:
Okay so here is the first result, this is untested. But if someone wants to test it go ahead. My phone isn't unlocked yet
You could first try flashing test_boot.img to boot partition and see what it does (you should be on 13.0.13.0 stock), if that doesn't work you could try flashing dtbo.img to the dtbo partition.
Please make a backup first! This probably won't work.
Click to expand...
Click to collapse
well Im going right now try it on pixelexperience 12.1. after that I give some feedback
well, phone instantly boot in to fastboot so nothing there, I was thinking if the source code is not out yet, then what source is used to create kernel for PE roms?
Samuel Ladziansky said:
bueno, voy ahora mismo, pruébalo en pixelexperience 12.1. después de eso doy algunos comentarios
bueno, el teléfono se inicia instantáneamente en fastboot, así que no hay nada, estaba pensando que si el código fuente aún no está disponible, ¿qué fuente se usa para crear kernel para roms PE?
Click to expand...
Click to collapse
Stock kernel
hmmm, so they edit only ramdisk to get it work with PE, interesting
I do little searching and found this...
GitHub - javashin/android_kernel_xiaomi_bengal at 11.0-gcc
MoonBase™ CAF MSM-4.19 kernel source for POCO M3 / Redmi 9T [Fury-Bengal] [Force-Fast-Foward] /.PUSH./ - GitHub - javashin/android_kernel_xiaomi_bengal at 11.0-gcc
github.com
EDIT: here is original source from is forked https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lime-q-oss
is for "bengal" board but not SM6225 (sdm665) but SM6222 (sdm662)
but I think when we use kernel configuration from stock kernel (like in /proc/config.gz) we maybe get working kernel?
I am going to try it, I downloaded it and we will see
This seems interesting. Does it work as nicely as the kernel extracted from MIUI that all these custom ROMs are using?
The time is over, guys.
Behold the source!!!
GitHub - MiCode/Xiaomi_Kernel_OpenSource at spes-r-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
Related
No ROM support
I think the sources have been released just recently, that means that the developers barely had any time to start development. I just flashed Xiaomi.eu rom, looks really promising to me because I didn't have many issues with stock rom.
No sources released yet... Maybe wait another 6 month's...
Yep no source release.... For sure last xiaomi phone!
Trimis de pe al meu MI MAX 2 folosind Tapatalk
There is a lineage is 14.1 ROM and mokee ROM then why anybody try to build or port other ROMs ? I'm a doctor not a developer but I tried to port but without much knowledge very difficult for me but any one developer can try.
So long story short, I signed up on 4PDA because my device wasn't getting any love here on XDA, and I found among other things, a working root method, 2 TWRP ports, a kernel compatible with Android 7.0 (thanks to my good friend LWJGLRobot), and an unofficial LineageOS 13 port with a WiFi bug (not gonna post any links, since I'm a new user, and anyway linking to 4PDA threads is forbidden). Now, however, I want to give back to the developer community on both forums, and also build AOSP for the heck of it. So far, I have the modified kernel (kudos LWJGLRobot), and I *may* be able to extract the vendor blobs, but I cannot, for the life of me, figure out how to build or extract a device tree. All the tutorials I've found on extracting device tree require that I have an Ubuntu VM. But since I'm doing the actual building on Google Cloud, I either need a way to upload my boot.img to the VM instance, or find a method that works with Windows. Is there a sibling device? If so, how do I modify its device tree to work on my device? Also, do I need to make modifications to the device and vendor trees depending on Android version? Any help would be greatly appreciated, as I've already done the repo sync for the AOSP source, and am finding this a formidable obstacle to overcome. If it helps, the SoC is MSM8916, and I'm currently running aforementioned LineageOS 13 port.
officialvelocifaptor said:
So long story short, I signed up on 4PDA because my device wasn't getting any love here on XDA, and I found among other things, a working root method, 2 TWRP ports, a kernel compatible with Android 7.0 (thanks to my good friend LWJGLRobot), and an unofficial LineageOS 13 port with a WiFi bug (not gonna post any links, since I'm a new user, and anyway linking to 4PDA threads is forbidden). Now, however, I want to give back to the developer community on both forums, and also build AOSP for the heck of it. So far, I have the modified kernel (kudos LWJGLRobot), and I *may* be able to extract the vendor blobs, but I cannot, for the life of me, figure out how to build or extract a device tree. All the tutorials I've found on extracting device tree require that I have an Ubuntu VM. But since I'm doing the actual building on Google Cloud, I either need a way to upload my boot.img to the VM instance, or find a method that works with Windows. Is there a sibling device? If so, how do I modify its device tree to work on my device? Also, do I need to make modifications to the device and vendor trees depending on Android version? Any help would be greatly appreciated, as I've already done the repo sync for the AOSP source, and am finding this a formidable obstacle to overcome. If it helps, the SoC is MSM8916, and I'm currently running aforementioned LineageOS 13 port.
Click to expand...
Click to collapse
hey could you send me the rom link in a private message or in other place outside xda because i couldn't find any rom for my zb500kl
sorry if my reply is not helpful but i really need a custom rom because ZenUI sucks
med99 said:
hey could you send me the rom link in a private message or in other place outside xda because i couldn't find any rom for my zb500kl
sorry if my reply is not helpful but i really need a custom rom because ZenUI sucks
Click to expand...
Click to collapse
Sure, no problem. I'll send you a link to LineageOS, or if you so desire, Resurrection Remix. I'm no longer using this device, and Google invalidated my payment details on Google Cloud anyway. Just PM me and tell me which ROM's link you want.
Asus_x00ad could you send me a link? [podrías enviarme enlace?]
Mod edit - translated by https://www.deepl.com/translator:
It turns out that I'm still looking for how to install some alternative cooked and rom recovery, I see that this rum link has Wi-Fi problems. Do you know if it has advanced in the subject so that it works or other alternatives?
Thanks in advance
************************
Resulta que sigo buscando como instalarle algún recovery cocinado y rom alternativa, veo que este enlace de ron tiene problemas de Wi-Fi sabéis si se ha avanzado en el tema para que funcione u otras alternativas?
Gracias de antemano
Hello all,
Been doing some research about custom roms for this device, found out that there is a guy on github named navarobot which posted a version of LineageOS:cm-14.1 for this device.
The are plenty of resources on his hub:
GitHub - navarobot/android_device_asus_ASUS_X00AD_2: cm-14.1 only. Asus Zenfone Go ZB500KL (X00AD).
cm-14.1 only. Asus Zenfone Go ZB500KL (X00AD). Contribute to navarobot/android_device_asus_ASUS_X00AD_2 development by creating an account on GitHub.
github.com
the only thing missing is a link to an img file, so if anyone knows how to make an img file from sourceCOde, it will be great to share the img with us.
cheers
Can not post links. Just type in google: "Xiaomi_Kernel_OpenSource cactus-o-oss" and to to GitHub.
Source it`s here
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cactus-o-oss
What does this mean, can developers now develop roms for 6a?
Helplease8998 said:
What does this mean, can developers now develop roms for 6a?
Click to expand...
Click to collapse
I think - Yes. Also maybe anyone can compile now x64 kernel for our x64 cpu device (at this moment we have only x32 kernel).
@Dreyk007
we still don't have a working vendor and tree. the only thing that matters for me right now is a working vendor considering from what i know it's the answer to getting voLTE to work on GSI rom's.
Ruskovskyy said:
@Dreyk007
we still don't have a working vendor and tree. the only thing that matters for me right now is a working vendor considering from what i know it's the answer to getting voLTE to work on GSI rom's.
Click to expand...
Click to collapse
All device tree here:
https://github.com/xiaomi-mt6765
atmouse said:
All device tree here:
https://github.com/xiaomi-mt6765
Click to expand...
Click to collapse
does this include the specific vendor? proprietary ones don't seem to be useful as far as i know. I plan to get on device development when my new PC is built (2 weeks-1 month) since i know the basics already.
Ruskovskyy said:
does this include the specific vendor? proprietary ones don't seem to be useful as far as i know. I plan to get on device development when my new PC is built (2 weeks-1 month) since i know the basics already.
Click to expand...
Click to collapse
There's some dude trying to build LOS 15.1 on Telegram Groups, the RIL isn't working unfortunately.
Just a question for the future. Are there custom roms like Lineage OS coming for Mi 11 Ultra?
Probably just a matter of time....
It's available for most of the earlier devices already: https://www.cyanogenmods.org/lineageos-18-mi-10-pro/
I don't think it will show up anytime soon...
When I got MiNote10, it was one of few phones with new 108MP camera sensor, developers had bad time trying to find drivers, or do anything to be able to use camera, as Xiaomi release only part of source code for this phone. As for now, there is no official LOS for MiNote10, just UNOFFICIAL, and the phone was released around November 2019 ?
MI11 Ultra also have new camera sensor GN2, display on the back, new chipset, I wish to see LOS or other custom ROM, but I know how hard is to build custom ROM for new hardware if you don't have drivers/source code.. Only hope in Xiaomi if they release complete source code needed to build ROM.
We'll have to wait for the popularity of this phone to go up first. Might take a while. But with miui12.5 being the crap fest that it is right now... I hope we don't have to wait too long for an aosp based ROM to come out
I would voluteer for testing... anything is better than this miui crap. So, anyone, please DM me, if you need a tester.
And put TWRP on the list. I might suffer from a good old fashioned paranoia, but kind if don't trust the current distributions of TWRP for the MI11U.
hello forum users please help these people, they were able to assemble the kernel from the sources, but as it turned out they are complete, but when checking the compiled kernel, the bootloop after the Poco logo was tested on the POCO M3 PRO
GitHub - RE800T/kernel_xiaomi_camellia
Contribute to RE800T/kernel_xiaomi_camellia development by creating an account on GitHub.
github.com
here is the compiled kernel repository
Please help
PS. POCO M3 PRO AND REDMI NOTE 10 5G = ONE SMARTPHONE
Я больше не буду said:
PS. POCO M3 PRO AND REDMI NOTE 10 5G = ONE SMARTPHONE
Click to expand...
Click to collapse
it's obvious, anyone can fingd this information on internet. this project is interesting. but i didn't see in this this section active users with necessary skill for a kernel compiling. most of this they still haven't figured out the right way to flash a gsi
I try to attract a lot of developers to help these people who could help them build and fix kernel problems and fix the touchscreen in TWRP and we also install GSI via fastboot
Я больше не буду said:
I try to attract a lot of developers to help these people who could help them build and fix kernel problems and fix the touchscreen in TWRP and we also install GSI via fastboot
Click to expand...
Click to collapse
it is a good initiative. I am a good modder but unfortunately at the programming level I am poor. I hope you will find someone able to do that. but I think it's not easy. until now no one has succeeded
PS: actually flash gsi is possible and for my experience also very simple
thank you, I will try to find people who will help if you want to help in some way, you are always happy
wetito said:
it's obvious, anyone can fingd this information on internet. this project is interesting. but i didn't see in this this section active users with necessary skill for a kernel compiling. most of this they still haven't figured out the right way to flash a gsi
Click to expand...
Click to collapse
And having flashed 6 GSI make you important? especially when you tell me that you have to root my phone to install a GSI or that you can't use "XiaomiADBFastbootTools" if you don't have Linux LOL I use it every day under Windows and yet I'm in dual boot with Linux Mint.
have a good day
Glucksnip said:
And having flashed 6 GSI make you important? especially when you tell me that you have to root my phone to install a GSI or that you can't use "XiaomiADBFastbootTools" if you don't have Linux LOL I use it every day under Windows and yet I'm in dual boot with Linux Mint.
have a good day
Click to expand...
Click to collapse
you didnt understant what i have said. probably my English is not perfect. ps: i have modded my first phone with android 4.1 firmware. so i have flashed more than 6 gsi. HOWEVER THIS DOESN'T MAKE ME MORE IMPORTANT, I'M NOT A PRESUMPTION
the fact remains that these problems do not concern me, and I might even avoid trying to help. rather you who are so good, why not create a detailed guide where you explain how to flash a gsi without risking ibootloop? I could also do it, but I gladly leave the honor to you.
xiaomifastboot tools for linux i'm talking are these. is a java script, probably work also under win, but under linux are better and easier to use
pps. LINUX MINT?!? WOW I'M IMPRESSED. LOL
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com