Thread closed.
For new thread , go to this link.
https://forum.xda-developers.com/le...t/kernel-kali-nethunter-t3813746/post77016833
I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Atharva Ambre[AT said:
;76155798]I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Click to expand...
Click to collapse
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Atharva Ambre[AT] said:
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Click to expand...
Click to collapse
Wrong architecture maybe? Z2 is arm64.
JashanjotSidhu said:
Wrong architecture maybe? Z2 is arm64.
Click to expand...
Click to collapse
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Atharva Ambre[AT] said:
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Click to expand...
Click to collapse
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
JashanjotSidhu said:
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
Click to expand...
Click to collapse
Ya sure
Note the major errors are in proc.c
Atharva Ambre[AT] said:
Ya sure
Note the major errors are in proc.c
Click to expand...
Click to collapse
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
JashanjotSidhu said:
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
Click to expand...
Click to collapse
Oh I'm sorry my bad here's the right file
Atharva Ambre[AT said:
;76282414]Oh I'm sorry my bad here's the right file
Click to expand...
Click to collapse
Sorry again same wait take this
Atharva Ambre[AT] said:
Sorry again same wait take this
Click to expand...
Click to collapse
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
JashanjotSidhu said:
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
Click to expand...
Click to collapse
Will try and I got it from github its the open sources kernel , its available on most of the ROM first page , I got it from aex intro page on XDA
U won't find it bcoz the CPU freq file is inside Linux/include/CPU so its not android based file it's the main working of Linux so u won't find any specific chip based also it won't mention sd820 bcoz its open source u can port it as long as u are able to get it right without bugs its an open source so its open for many devices and many chipsets.
Update :
I tried again from start I think its the problem with the compiler of ndk will download older version and try out tomorrow...still getting many other errors while compiling from the source kernel
Pls provide me the link of latest stable ROM with it sources updated!thank you!
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Atharva Ambre[AT] said:
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Click to expand...
Click to collapse
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
Idk I have just right now running Ubuntu on VM I m downloading the files I don't think so that the problem is associated with kernel version bcos the thing is many new Android devices like one plus 3 and other many update android version devices like nexus have official nethunter support so latest android means the kernel will be upgraded to more newer version such as 3.18.xx and all so is our z2 plus to the same version ....anyways gonna give a try in Ubuntu or else have to wait till I get a proper source for kernel.
Can u suggest any good source for this project ?
I'm currently using the Oreo ROM and the source of the kernel is DDrb0h kernel which is the branch of lineage 15.1.
Also I have identified the major error which is in CROSS COMPILE step for android ndk idk why but in Kali Linux I'm not able to get CROSS COMPILE so kinda in lil problem...
JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
I think the problem is associated with the kernel sources same error on ubuntu
Update
Tried my best to compile yet ran into another error
Changed the sources to latest treble one
I got new error with arm-linux-androideabi- gcc error some command is invalid ....I require a little guidance here . So kernel developers pls show me which version of ndk shld I use and sources shld I refer and what extra commands shld I run?
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
SteelBodyX said:
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
Click to expand...
Click to collapse
Thank you for ur suggestion. Ya I haved pm him already but didn't receive any update from him and also the work is done.I have made the changes for the project just one step I'm lagging is compiling it......then its free for distribution here.
Related
Hey folks! :highfive:
Source code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
Github repo: https://github.com/redmi1s-dev/lk
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-27
What's the purpose of this?
sinnerz2000 said:
What's the purpose of this?
Click to expand...
Click to collapse
I think you can achieve dual boot with this. Not sure tho.
Syssx said:
I think you can achieve dual boot with this. Not sure tho.
Click to expand...
Click to collapse
If you really want, you can boot WinRT too.
hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master
where is the sources?
thewisenerd said:
hi OP,
you forgot to add links in first post...
Anyways, do we see GRUB being ported in the near future? I can see some armani related changes here: https://github.com/grub4android/lk/commits/master
Click to expand...
Click to collapse
pgreed said:
where is the sources?
Click to expand...
Click to collapse
Take a look at Downloads tab.
Grub is already ported, and working. :angel:
balika01 said:
Hey folks! :highfive:
Soruce code of bootloader has been reversed, and released to github! :victory:
To install it, you have to build the source, the flash the emmc_appsboot.mbn to aboot via fastboot.
XDA:DevDB Information
LittleKernel - Bootloader, Device Specific App for the Xiaomi Redmi 1S
Contributors
balika01, m11kkaa
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-26
Last Updated 2014-10-26
Click to expand...
Click to collapse
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for
balika01 said:
Take a look at Downloads tab.
Grub is already ported, and working. :angel:
Click to expand...
Click to collapse
There ain't no 'downloads' tab :|
rohit choudhary said:
if anyhow you could make dual boot possible id be very very thankfull:good:
this is the only thing i was waiting for
Click to expand...
Click to collapse
You can make it, but you have to repart your nand. This is dangerous, and you can easily make a brick.
Reversed? How you reverse engineered on Bootloader?
Forever Alone said:
Reversed? How you reverse engineered on Bootloader?
Click to expand...
Click to collapse
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.
balika01 said:
I bought IDA Pro + x86 and ARM Hex-Rays decomplier, then i just reversed the changes between CAF jb's lk and Mi's bin.
Click to expand...
Click to collapse
can you do it with kernel too bro????
Hey.. can someone fetch me link of working build of grub? Caz I got some multiboot stuff coming up for our armani.
Multiboot isn't really that useful on our phones since we'll be flashing android anyway, if we had say Ubuntu and android dual boot then that would be something
We got grub workin on our device.... Ubuntu ain't no impossible-thing I guess... mate... Just to kick things off.. android dual boot would do.
device with Same configuration exists with kernel source out
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Belive me it's not that simple.
Rohitdahiya said:
Kernel source for RedMI 1S might not be available but a device with same configuration is there and kernel source exist for it. I think this may help the developers
http://forum.xda-developers.com/showpost.php?p=56057091&postcount=76
http://www.xolo.in/q1100
Click to expand...
Click to collapse
Source for msm8226 has been released by qcom. When i try to boot it, it just crash whitout last_kmsg. (I think stg free it, before lk starts running. F*ck xiaomi.)
(In code msm8228 same as msm8226, thats why cpuz says msm8226.)
Most Apps reads from what data are given in the system files.
Lets say, the build.prop itself says msm8226, and if you dig around in the / (root) folders, almost all files are for msm8226 cpus.
I still dont get, why the hell did XIAOMI implemented msm8226 drivers and other details for msm8228 cpu.!!!!!!
http://downloads.sourceforge.net/pr...xz?r=&ts=1439784880&use_mirror=skylineservers
SHA1: 463f818fc8b57525981a46e31ea5ee63f2987742
MD5: 88d8db5d4c9637daeb339eb79878c93a
Mirror: https://mega.nz/#!j4s1WYLK!DpK2bMfznrt_ih3-UtE6xvUgFSAujw9LBu4qgSCSzkU
Thanks to @neilownz for notifying us in the system image thread! Let the rom development begin!
Oh and xposed framework also works for the idol 3 as of yesterday.
Click on mirrors. I already finished downloading it in case it disappears.
Yay. Let the development begin
Yes, thx alcatel !
thanks for noticing
damn you've been faster than me
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
frankee207 said:
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
Click to expand...
Click to collapse
Yes it is. Plus 1.8 GB external tools.
Game of Roms.
Roms are coming...
My favourite season of game of ROMs xD
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
yazzabo said:
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
Click to expand...
Click to collapse
No, the 6045 has a 64bit Snapdragon 615. The OnePlus One has a 32-bit Snapdragon 801.
someone could compile a kernel?
cpu -snap615-msm8939
board msm8916
32bits-arm.......64 bits -Aarch64 for gcc? or armv8?
arm64-defconfig
gcc version for compiling?
Woohoo cyanogenmod (or another ROM) here i come!!!
Successful compilation
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series? I'm waiting for the day someone generates a kernel with some of the newer governors like intellidemand or interactiveX...perhaps would solve any of the remaining lag and heat issues. I honestly thought they would have made factory rom downloads available first before source but certainly won't complain.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
franq36 said:
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
Click to expand...
Click to collapse
I use the prebuilts from the Cyanogen repo. Also the recommended architecture of the host machine for compilation of Android is x86_64 from long time.
@franq36 ... In case that you are curious. This is the list with the installed gcc packages on the host machine.
Code:
gcc install
gcc-4.7 install
gcc-4.7-base:amd64 install
gcc-4.7-multilib install
gcc-4.8 install
gcc-4.8-base:amd64 install
gcc-4.8-multilib install
gcc-4.9-base:amd64 install
gcc-multilib install
franq36 said:
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
Click to expand...
Click to collapse
Here are two logs from my virtual machine. The first build is for 32 bit architecture while the second is for 64 bit. The TARGET_KERNEL_ARCH in both cases however is arm. arm64 cannot be compiled successfully, as returns the following error:
Code:
make[2]: *** No rule to make target `zImage'. Stop.
make[1]: *** [sub-make] Error 2
franq36 said:
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
Click to expand...
Click to collapse
I don't understand what you mean here. The idol347 however is with Snapdragon 410 not 401.
franq36 said:
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
Click to expand...
Click to collapse
This is strange indeed.
---------- Post added at 19:52 ---------- Previous post was at 19:10 ----------
famewolf said:
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series?
Click to expand...
Click to collapse
I'm not sure about this. The devices are different, the boards are different, the kernel configuration and respectively the kernel is different, the display resolution of the devices is different. These are too much differences I think.
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
i think you can contact the guy named mario tomas serrafero hes the one that writes the main page articles
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
for now it is early, still are not completely operational ... I think for 6045
and I managed to fix compilation errors through installed ubuntu 14.04.3 64 bits and all the tools ...
idol3_defconfig is only arm64 and gives -mgeneral-regs-only error.
I could cheat and load it from arm but having to fix several compilation errors and dependencies bad in defconfig.
I am having many compilation errors which explains that the GCC is not quite right. NDK official gcc 4.9. arm-linux-androideabi have to look any more current or Linaro to check
I think there is a gcc 4.9.3
I'm half compilation with many problems ... I hope it's not the fault of sources and it is time lost
has any one started on porting CM12/12.1 ? you could count on me for testing
Due to several reasons I have stopped the deployment of the "monthly Update.Zip packages" !
Thanks for your understanding.
This thread will be used for the unified tegra-3.18 kernel only.
Twelve:
tegra-3.18_unified_dragon_kernel_12_v211213.zip
Eleven:
tegra-3.18_unified_dragon_kernel_11_v201218.zip
Ten:
tegra-3.18_unified_dragon_kernel_10_v201010.zip
Pie:
tegra-3.18_unified_dragon_kernel_p_v200310.zip
Oreo:
tegra-3.18_unified_dragon_kernel_o_v200310.zip
Changes/Features:
- Upstream to kernel version 3.18.140
- Various patches and security updates
- Added Wireguard support
- Added/Enabled various file systems (exFat, NTFS, Network Filesystems .. etc.)
- Changed kernel config to enable/improve support for varioius services (tethering .. etc.)
- Added "fix cpu frequency limitation"
- etc.
Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !
The package contains an Image.fit kernel binary only - and no ramdisk part !
This way the kernel should run on all available Android Oreo/Pie/Ten ROMs for the dragon device.
And there is no need for a new SuperSu/Magisk installation afterwards, unlike to "full boot.img" installation.
Sources:
https://github.com/followmsi/android_kernel_tegra
https://github.com/followmsi/lazyflasher/tree/followmsi-dragon
https://github.com/followmsi/AnyKernel2/tree/dragon
Download:
https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn
Big thanks to @NYCHitman1 (Dirty Unicorn), @cheep5k8 (xceed), @Vartom and updateing from Team Mokee for the nice kernel sources !
Big thanks to @osm0sis (Anykernel2) and @jcadduono (lazyflasher) for the nice tools !
Enjoy
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
dmitrygr said:
flashed your system image
devices does not boot
flashed back to stock
boots
edit: further details
every boot just dumps me into recovery.
Click to expand...
Click to collapse
Thanks for feedback .. no good news.
Sorry, I can not reproduce your problem.
Tested the system_vendor udapte.zip several times on my Pixel C.
No problem so far ...
You flashed the complete .zip via TWRP ?
What was your previous firmware level ?
Did you upgrade bootloader as well ?
What kernel do you have in use ?
EDIT:
Which Version of TWRP ?
Pls use xceed version for now.
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
followmsi said:
The NYChitman1 version seems to have problems.
http://forum.xda-developers.com/pix...ock-bootloader-install-custom-t3307183/page14
Click to expand...
Click to collapse
Only the latest one I released because I didn't put the proper flag in place -- the previous one works perfectly fine as indicated by myself and others.
Also, I find it interesting that you've created a development thread while you aren't actually developing anything.
Thanks for the update.
Still like to test your version.
Ok, the version from here is recommended .. http://forum.xda-developers.com/showpost.php?p=66557703&postcount=101
In the one from yesterday you fixed vendor image flashing via TWRP.. sounds nice.
When do you re-release this version ?
You may open a new thread for your TWRP releases ..
Thanks a lot for all your work!
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
followmsi said:
New kernel released ... pls test
Update.ZIP_Nexus_Ryu_chromeos-3.18-kernel_v160519_followmsi.zip
There are lot of changes in compare to latest stock kernel .. https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18/
Cheers
Click to expand...
Click to collapse
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
redukt said:
Many thanks for your work The kernel is for stock / AOSP roms? Running Dirty Unicorns and I think it´s not compatible :/
Click to expand...
Click to collapse
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
nic. said:
Any chance of getting a port of multirom? Let me know if there's any interest, and what I can do to help.
Click to expand...
Click to collapse
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
followmsi said:
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
followmsi said:
Sounds good .. have it running on Nexus 7 flo .. really like it.
MultiROM for PixelC would be really nice .. the chromeos is part is maybe tricky.
But like SuperSU .. automatic chromeos image unpack and repack, if required at all.
It seems Tassadar is not around anymore .. not sure if he will come back.
Some new guys have taken over .. they just made a new update release for TWRP and MultiROM..
Works fine
Are you able to port it to Pixel C ?
Thanks
Click to expand...
Click to collapse
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
redukt said:
Bootloop
Restored my Nandroid and device is up
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
Thanks for the test ..
Restore DU boot.img and you are back to normal ..yep
I will unpack the DU boot.img and have short look .. just to check it.
nic. said:
I am wanting to dig into the Linux4Tegra side of this, and was hoping that some of the work for multirom could or had been done. I don't know anything about the chromeos bootloader. Looking into it, Chrubuntu might be a viable path for this. I feel like this device is gimped with Android.
Click to expand...
Click to collapse
Sounds like a lot of work .. but if you have the right people involved ..
Maybe xceed or nychitman will know better how to "manage" the bootloader ..
As I know, until today, "nobody" knows how to remove the 30 second warning time beep sound ****.
Right now I am happy to "manage" the layer above .. boot.img and recovery.img
redukt said:
DU is CM based and unfortunately incompatible :/
Click to expand...
Click to collapse
What are you talking about? We're not CM based.
followmsi said:
There are so many fixes since MXC89F kernel .. which was commited on Arpil 5th .. even it's the May release. Ok, was tagged on May, 4th.
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/MXC89F
Last changes .. 6 weeks ..
https://chromium.googlesource.com/c...+log/9c052efad6e651d33334b84c8f1feaf8945e8e7a
I am running the new kernel on latest M stock release .. MXC89F.
No problems so far .. really stable.
The kernel should run on all stock M releases for PixelC.
Used latest stock ramdisk to build the kernel .. maybe the dirty unicorn ramdisk is different.
But the actual kernel should work as well ..it's a dragon kernel.
Repack DU ramdisk with my kernel and it will most probably work as well .. maybe even with the same ramdisk, without repacking. Needs to be tested ..
Give it a try .. it will not hurt.
Cheers
Click to expand...
Click to collapse
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
NYCHitman1 said:
What are you talking about? We're not CM based.
Click to expand...
Click to collapse
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
NYCHitman1 said:
What are you talking about? We're not CM based.
I had been keeping up with the chromeos-3.18 branch upstream, but I realized that a majority of the commits do not even apply to Dragon -- so it wasn't all that worthwhile to have in the majority of cases. With that said, I decided to go back to the MXC89F source until the next batch of source is released in June.
Click to expand...
Click to collapse
You are right .. there also many fixed not relevant for dragon at all.
But it´s a fresh kernel .. upstream
I was so free .. and made a new DU kernel now .. used your ramdisk and my fresh chomeos-3.18 build from today.
@redukt, please test this kernel again .. on DU
Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks .. still bootloop ?
redukt said:
Well my bad...DU is AOSP based. I get mixed up with all several custom roms on my devices :silly:
Click to expand...
Click to collapse
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
followmsi said:
Please test this one ... Update.ZIP_PixelC_Ryu_chromeos-3.18-kernel_DU_v160519_followmsi.zip
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Thanks !
Click to expand...
Click to collapse
!!! Device is booting!!!
Meh... forget to install SU lol.... Will have a look in kernel auditor
Many thanks
edit: I have to flash the latest supersu (beta v2.74-2) to get root again. Will test your kernel til the next DU weeklie as dd. I´ll have a look at the frequency overview and kept stock settings / governor. System runs fluid with no hickups or so. Great work!
Looks also very interessting ..stabilize-smaug-7897.B-chromeos-3.18
https://chromium.googlesource.com/c...kernel/+/stabilize-smaug-7897.B-chromeos-3.18
Will see .. today they released the 3rd N preview ... maybe it´s time for some N testing.
As I understand correct .. using N ramdisk and the same kernel from today should work on N as well.
We will see ...
Cheers
I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot. I tried to boot lp-kernel from @premaca it booted.
Also, my compiled compiled kernel size is a megabyte bigger than the great premeca's.
I used the config file from premeca's source & kernel.
@ premeca, Please help me .............
Which compiler should I use ?I used ndk
& the one from Google source.
Thanks in Advance!
I want to compile final-lp version.
EDIT:-
Fixed it myself,
I was using Ubuntu's preinstalled Archiver to extract the Kernel source zip.
Using "unzip *.zip" solved the problem (idk why).
Just get the source, download toolchain from googlesource
And follow the steps in video
Naveen Singh said:
I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot:...
Click to expand...
Click to collapse
I've never built a Kernel but, I believe that the following thread is the closest to what your looking for that's specific to the Redmi 2.
https://forum.xda-developers.com/showthread.php?t=3155130
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Naveen Singh said:
I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot. I tried to boot lp-kernel from @premaca it booted.
Also, my compiled compiled kernel size is a megabyte bigger than the great premeca's.
I used the config file from premeca's source & kernel.
@ premeca, Please help me .............
Which compiler should I use ?I used ndk
& the one from Google source.
Thanks in Advance!
I want to compile final-lp version.
Click to expand...
Click to collapse
Found any reason why it didn't boot? you have any ramoops file or something so you can know better? Link your kernel source for better help.
Some say it's compiler.
premaca said:
Found any reason why it didn't boot? you have any ramoops file or something so you can know better? Link your kernel source for better help.
Click to expand...
Click to collapse
@premaca
I used your kernel source for redmi 2 lollipop.
https://github.com/premaca/Xiaomi_Kernel_OpenSource/tree/Final-LP
Some people say that it maybe wrong compiler.
I also think so because my compiled zImage size is bigger than the one you have already compiled.
Yourcompiled kernel booted successfully. ( here it is )
Which compiler do you use to compile kernels for redmi 2 ?
Kernel 4.9 for Redmi S2/Y2
After hours of working and porting, I present to the community stable linux kernel 4.9.
This is the LTS msm-4.9 linux kernel maintained by Codeaurora Forum ported for our device from the base 3.18 kernel.
what works?
Boots
Touch
Wifi
RIL (calling, mobile data etc)
Sound
Fingerprint (FPC And Goodix)
Front Flash
Torch
Camera
Vibrator
IR Sensor
Bugs:
You tell me!
A big thanks to @lostark13 for bug fixing and @33bca for his amazing work on 4.9.y for Daisy
You can find the source here!
XDA:DevDB Information
Linux Kernel 4.9, Kernel for the Xiaomi Redmi S2
Contributors
m_vaisakh, lostark13, 33bca
Source Code: https://github.com/mvaisakh/android_kernel_xiaomi_msm8953
Kernel Special Features:
Version Information
Status: Stable
Created 2020-04-20
Last Updated 2020-04-27
PERU
Awesome work by peru's team ?
Awesome man!
great job... :good:
Awesome ?
Noice
Can we use it on miui rom?
Mr.smmm said:
Can we use it on miui rom?
Click to expand...
Click to collapse
It is a 64 Bits kernel I think ... so .... no ?
xNiux said:
It is a 64 Bits kernel I think ... so .... no ?
Click to expand...
Click to collapse
Or maybe yes ... Because it is only source and no binary ... So maybe we can compile Both : 32 and 64 bits ....
But how compile it ? I can try, but I don't know the command line ... Just ... make ?
xNiux said:
It is a 64 Bits kernel I think ... so .... no ?
Click to expand...
Click to collapse
Yes it's 64bit only kernel.
xNiux said:
Or maybe yes ... Because it is only source and no binary ... So maybe we can compile Both : 32 and 64 bits ....
But how compile it ? I can try, but I don't know the command line ... Just ... make ?
Click to expand...
Click to collapse
You can't compile 32bit, it was never my intention to create 32bit.
I can give more than 10 reasons why 64bit is just better than 32bit
m_vaisakh said:
You can't compile 32bit, it was never my intention to create 32bit.
I can give more than 10 reasons why 64bit is just better than 32bit
Click to expand...
Click to collapse
Understand and aggre with you ! ^^
Could you give us the the compiled img please ? or help me to compile it ?
xNiux said:
Understand and aggre with you ! ^^
Could you give us the the compiled img please ? or help me to compile it ?
Click to expand...
Click to collapse
for the sake of god don't try now to compile 4.9
some bugs are possible to fix only with on device tree " and this is private only " like fingerprint , video , internal storage error message , etc
so your only option is to wait a rom with 4.9 as prebuillt "will come soon "
Its_Vixano said:
for the sake of god don't try now to compile 4.9
some bugs are possible to fix only with on device tree " and this is private only " like fingerprint , video , internal storage error message , etc
so your only option is to wait a rom with 4.9 as prebuillt "will come soon "
Click to expand...
Click to collapse
Ok ! Thanks !
how to install?
Sadik283 said:
how to install?
Click to expand...
Click to collapse
Install a rom which is use it (HavocOS 3.5 for example)
How to download? Link?
peru work by peru men
bro how did u port like this??did u take linux kernel 4.9 and added device specific drivers to it from 3.18 that's it or something more ??