Keep in mind, this is not the official source, it has no Xiaomi changes, but it might be helpful for someone.
The Redmi Note 11 has the SM6225 SoC, codename khaje.
The reason why we didn't get the kernel source is because our phone is GKI compatible, which means the kernel source has been clean and out since the beginning.
Khaje-idp is the dts you should use as base for this phone, as the original dtb is based on the same.
Devicetree for khaje is here
GKI kernel source
Config for building the kernel can be taken from arch/arm64/configs/vendor/bengal-perf_defconfig , or from doing adb pull /proc/config.gz on your own phone, then extracting the file from inside.
Bengal runs 4.19. I don't see how its GKI considering 4.19 has the barebones gki implementation and 5.4 was the first actual gki implementation
cyberknight777 said:
Bengal runs 4.19. I don't see how its GKI considering 4.19 has the barebones gki implementation and 5.4 was the first actual gki implementation
Click to expand...
Click to collapse
5.4 was the first one, but it seems other versions got backported too, can't tell much other than that
sonic011gamer said:
5.4 was the first one, but it seems other versions got backported too, can't tell much other than that
Click to expand...
Click to collapse
That's an IoT tag dude.
cyberknight777 said:
That's an IoT tag dude.
Click to expand...
Click to collapse
My bad then
sonic011gamer said:
Keep in mind, this is not the official source, it has no Xiaomi changes, but it might be helpful for someone.
The Redmi Note 11 has the SM6225 SoC, codename khaje.
The reason why we didn't get the kernel source is because our phone is GKI compatible, which means the kernel source has been clean and out since the beginning.
Khaje-idp is the dts you should use as base for this phone, as the original dtb is based on the same.
Devicetree for khaje is here
GKI kernel source
Config for building the kernel can be taken from arch/arm64/configs/vendor/bengal-perf_defconfig , or from doing adb pull /proc/config.gz on your own phone, then extracting the file from inside.
Click to expand...
Click to collapse
i dont think gki compatible , since the kernel is still 4.19
Guan Yu said:
i dont think gki compatible , since the kernel is still 4.19
Click to expand...
Click to collapse
It definitely is GKI, the phone has the GKI layout too (even if it's 4.19), check it yourself with parted inside twrp (check every UFS lun)
Are ROM developers aware of this?
I'm working on it, but Im pretty sure it's not GKI. The layout is not saying anything as it is mandatory from android 11 and onwards I think. If you look at the kernel sources from Xiaomi for other devices (Lime for example) you will see that they aren't GKI either. All the drivers are inside the kernel source.
But without schematics and UART connection its pretty much impossible to get it booting (i did try finding uart by luck but dended up destroying my wifi/gps signal), but I am trying. Im kind of confused as of where the DTB lives because we only have a DTBO (overlay) partition and no DTB partition. Its also not appended to the kernel I think but Ill have to check again to be sure.
I found the dtb partition in vendor_boot partition.
Related
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired
Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source
I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel
Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?
http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
agentfazexx said:
http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
Click to expand...
Click to collapse
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
shabbypenguin said:
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
Click to expand...
Click to collapse
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
agentfazexx said:
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
Click to expand...
Click to collapse
you can make a rom without ever touching the kernel. and without kernel source all you can do is unpack it and edit the text files in the ramdisk. its not really hacking.
Hello,
I started making kernel builds again.
CHECK BELOW FOR IMPORTANT INFORMATION!
YOU MUST USE MIUI Q FIRMWARE PACKAGE FOR THIS KERNEL TO WORK. OTHERWISE YOU'LL END UP IN FASTBOOT MODE FOREVER.
Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs too, thus won't work until Xiaomi releases it's kernel source code.
FLASH THIS BEFORE FLASHING MY KERNEL. I UPLOADED FIRMWARE PACKAGE FOR YOUR CONVENIECE!
DOWNLOAD LINK FOR MIUI Q FIRMWARE PACKAGE
Flashing procedure is standard - through recovery. Magisk is optional, only if you want root.
*big thanks to rama982 for possible insights and some help from his side*
*nathanchance for android-linux stable and helping upstream our kernels*
*franciscofranco for commits that made our phone happier and snappier*
*sultanxda for his beastly development in Android scene and ridiculous understandment in kernels in general*
*also thanks to osm0sis for Anykernel3. Without this, flashing kernels would be a harder process to do*
XDA:DevDB Information
JellyKernelAlpha, Kernel for the Xiaomi Redmi Note 7
Contributors
airidosas252, rama982, nathanchance, Qualcomm, Code Aurora Forums, osm0sis, other developers
Source Code: https://github.com/airidosas252/Xiaomi_Kernel_OpenSource
Kernel Special Features: Stability, latest kernel sources
Version Information
Status: Testing
Created 2019-11-22
Last Updated 2020-02-01
DOWNLOAD LINK FOR GITHUB RELEASES
Due to different kernel base, older releases are irrelevant from now on.
UPDATE: I added a link for MIUI Q firmware package in the OP. Check it out and remember to flash it first before flashing my kernel. Thanks.
-------------------------------CHANGELOG------------------------------
Jelly Kernel Alpha 1.1.1 Hotfix
ALSA: pcm: Add missing copy ops check before clearing buffer (bootloop after voip videocall should be gone now)
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.1 beta release
IMPORTANT INFO! Camera won't work on a lot of ROMs due to imcompatible camera drivers in the kernel. This kernel uses a patch for MIUI Stable 11.0.4 release, which introduced updated camera blobs back in Android Pie. Double check, whether your ROM uses these blobs. MIUI Q uses different blobs, thus won't work until Xiaomi releases it's kernel source code.
If this kernel is not booting for you (going straight to fastboot mode), you need to use MIUI Q firmware package.
Changelog:
*Bringup for Clang 10 and it's now compiled with Clang 10
*Using LZ4 compression for zRAM
*Forcefully load modules (this should fix Wi-Fi problems on various ROMs)
*Rapid GC for F2FS filesystem
*Added fsync and crc check switches
*kgsl fixes and optimizations included
*Introduce additional NEON accelerated arm64 routines
*cfq io scheduler fixes and optimizations
*Tick rate increased to 300HZ for improved responsiveness
*CPU mask affinity set to 4 cores for improved efficiency
*Enabled F2FS filesystem support with encryption
*F2FS fixes
*Increased slmk's aggression rate to 192MB per app kill
*Enabled Dolby DS2 audio standard
*And more I don't really remember, check commit history for more detailed changes
-----------------------------------------------------------------------------------------
Jelly Kernel Alpha 1.0 beta release (don't use this release, it's deprecated)
*Complete rebase on jasmine's Q tag.
*Linux 4.4.211
*Adrenoboost enabled and set on low parameter
*Workqueques reworked for better responsiveness and lower power consumption
*Small UV for both CPU and GPU
*CPU Bitmasking
*DTB debloat (reduced kernel's footprint)
*LA.UM.8.2.r2-00600-sdm660.0 CAF tag
*Using older Wi-Fi CAF tag for better down/up speeds
And more stuff I don't remember.
-----------------------------------------------------------------------------------------
DISCLAIMER:
-There will be 1-3 kernel builds per week, unless there's nothing I can improve, then builds will be as is.
-Anyone, who has tested it already, give me some feedback in the comments.
-If you get freezes, crashes, restarts, write me up with a attached dmesg, log, anything, that can give me a clue what's wrong. Thanks. Happy JellyKernel'ing ^^
Where is the download link?
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Use the browser - there's a section DOWNLOADS above the thread. There you will find my kernel build. Cheers.
Zulwiczek1983 said:
Where is the download link?
Click to expand...
Click to collapse
Here, for short: https://forum.xda-developers.com/devdb/project/dl/?id=32079
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
airidosas252 said:
NEW BUILD IS AVAILABLE NOW!
Check higher posts for download link. Happy flashing!
Click to expand...
Click to collapse
Does it support Kcal? Regards :good:
rubentkato77 said:
Does it support Kcal? Regards :good:
Click to expand...
Click to collapse
Yes it does. Look up using kernel manager.
airidosas252 said:
Yes it does. Look up using kernel manager.
Click to expand...
Click to collapse
Thnk you, will flash to test :good:
Is the any chance to get the turbo frequencies on the GPU?
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
tekkaman7 said:
I read that on some other page I can't remember where, can you please why that supposed frequency is not on the stock kernels, does it take to much energy?
Click to expand...
Click to collapse
I believe Qcom left off this frequency just because CPU is already close to some of their flagship SOCs in terms of CPU performance.
Everything in the source code is left done, you just need to modify a code a bit and you have higher frequency. If you want to go any higher, you would need to modify the code a lot more. Tried it and gave up on that.
It could be anything, really.
Moreover, you don't see too many phones using this exact SOC.
P.S. Funny thing though, this OC feels like placebo effect, like CPU is running faster but it's really not.
Think about it, when sdm660 came out, it was between SD821 and SD835 in terms of CPU performance. GPU is more or less the same as Adreno 430.
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
airidosas252 said:
Gonna release new kernel build soon.
Still working out some quirks I come up every once in the while.
Stay tuned for news. Good day.
Click to expand...
Click to collapse
Thanks for your work, we will waiting :good:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
airidosas252 said:
NEW KERNEL BUILD AVAILABLE NOW!
As usual, check main page for a download link. Happy flashing!
Click to expand...
Click to collapse
thank you, downloading. :good:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
xiaomi.lim said:
Overclocked? Using Evira for now on MIUI 11 Pie, but Evira is outdated..... Can't support Android 10
So, hope can have Overclocked kernel support Android 10
Click to expand...
Click to collapse
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
airidosas252 said:
Yep, it's overclocked and it's for Android 10.
I've seen people running this with MIUI too.
Click to expand...
Click to collapse
Overclocked to ? 2.46GHz?
xiaomi.lim said:
Overclocked to ? 2.46GHz?
Click to expand...
Click to collapse
Yes, but I don't think I'll keep the OC for much longer. I really don't see the benefit of it.
Phone is already really fast and snappy.
I did a build with stock clocks and compared it to the OC one. And here's the surprise - there isn't almost any difference.
I fixed several known issues which bugged me a lot and those seem to remedy all of the problems I had.
Moreover, I hate overbloated kernels with features I don't use. I like being clean and compact.
Hi, the sound control (for speaker, earpiece and headphones) available or do you plan to add it in future? They get pretty handy really. I do appreciate keeping the kernel without much bloat though. : D
Most of us are aware that this device is running a 32-bit kernel on top of a 64-bit SoC.
After fiddling around with porting linux potentially to this phone (will come out once i manage to make something that ACTUALLY works), I found out that the Xiaomi 8A uses the EXACT same SoC (SDM439) and has a 64-bit kernel. Hmmm, maybe I can get 64-bit going on this phone I thought.
So what I did essentially was take a 8A kernel (that works) and add back the 7A defconfig changes.
I was sure it had no chance to work, but I tried it anyway.
It boots into Android without any issue... lmao
Since this board is pretty restrictive when it comes to attachments, I had no other choice but to upload to google drive.
Here's the link: [Outdated, look here instead -> https://forum.xda-developers.com/redmi-7a/development/64-bit-redmi-7a-t4145225]
Update: Everything works now, except some pretty minor bugs here and there.
Kernel source: https://github.com/nikp123/Xiaomi_Kernel_OpenSource/tree/pine64-p-oss
Wow... How interesting, I hope people can work something out of this, thanks
Turns out that the touch screen drivers are broken. Currently trying the opposite, building a 7A kernel using a "64-bit" defconfig, with the obvious changes so it compiles.
Wow !!! waiting for more update
Quick update: The stock kernel cannot compile with the ARM64 config. Will have to resort back to the 8A kernel for this.
Quick update 2: I've also broken audio and can't get it back.
yes ill be wating for this
This is really cool!! I'll definitely keep an eye on this thread
Update 3: Got touch screen to work
But I'm going to switch my kernel base to the Xiaomi stock kernel as it seems more stable.
Had to analyze a 14MB diff file to see what broke it 0_0
PS: Still haven't figured out how to get the audio back
Good luck!
Hope everything works soon
Update 4: Audio fixed
Only Wi-Fi left.
Update 5: The driver Wi-Fi seems to be missing from the kernel repo, that's why it doesn't work.
Merging it into the repository just like the audio driver might yield results.
nik1234567 said:
Update 5: The driver Wi-Fi seems to be missing from the kernel repo, that's why it doesn't work.
Merging it into the repository just like the audio driver might yield results.
Click to expand...
Click to collapse
Can't wait to try it
Update 6: Wi-Fi driver is giving me hell. Does anyone know a sane way to compile it, IT WOULD BE SO MUCH APPRECIATED.
nik1234567 said:
Update 6: Wi-Fi driver is giving me hell. Does anyone know a sane way to compile it, IT WOULD BE SO MUCH APPRECIATED.
Click to expand...
Click to collapse
can i know what base rom you test it?
daizu said:
can i know what base rom you test it?
Click to expand...
Click to collapse
Any 32bit ROM that works essentially
Update 7: Wi-Fi driver works when built as a kernel module. Kinda finicky, but that's that.
Now for vendor-space fixes.
Amazing! Thank you so much for sharing your advancements and development with us ?
May I ask: what will change on this device with a 64 bits kernel? I mean: what is gained? I'm pretty ignorant in the subject.
I want instruction for flashing boot.img ... Can i flash it on my current a64 custom rom? Or it needs to be on miui/stockrom?thanks
ModExplorer said:
I want instruction for flashing boot.img ... Can i flash it on my current a64 custom rom? Or it needs to be on miui/stockrom?thanks
Click to expand...
Click to collapse
Don't flash the kernel yet because it's not finished. Wait for the devs to release the final version unless you want bugs.
hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed