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.!!!!!!
Related
OTools------------------------------------------------------------------
OTools is an opensource toolkit for windows and linux that helps you manage your oppo or oneplus device.
Click to expand...
Click to collapse
Code:
This program has enough knowledge to brick your device, destroy your computer,
void warranties, eat cats and burn your flowers.
The developer disclaim every damange caused from the usage of this program.
Supported devices
------------------------------------------------------------------
OnePlus One
Oppo Find 7(a/s)
Oppo Find 5
Oppo N1
Features
------------------------------------------------------------------
User friendly gui
Management features
Backup and restore (adb)
Push and Pull files
Import camera photos
Install apk
Record Screen
Shell
Modding
Root
Unlock Bootloader
Lock Bootloader
Backup EFS
Flash zip files
Install roms (optional backup)
Flash boot.img files
Install recovery
Root Mode
Dipendecies
------------------------------------------------------------------
ADB
FastBoot
XTerm (only for linux amd64)
Downloads
------------------------------------------------------------------https://github.com/linuxxxxx/O-Tools
Sources
------------------------------------------------------------------
Github - Master
Windows
Linux (amd64)
Unix / Linux
Notes
------------------------------------------------------------------
It's fully written using qt (c++), some parts are written in bash (batch for windows), if you want to compile, just import the sources into qt
It's not avaible yet, I just got my opo, so NO ETA
It's based on my XiaomiTool
Contributions and suggestions are welcome
XDA:DevDB Information
OTools - An opensource Toolkit for Oppo and OnePlus devices , Tool/Utility for the ONEPLUS ONE
Contributors
linuxxxx
Source Code: https://github.com/linuxxxxx/O-Tools
Version Information
Status: Alpha
Created 2014-12-25
Last Updated 2015-01-16
Placeholders are not allowed on XDA. When are you going to fully release it with a downloadable file?
TiVON said:
Placeholders are not allowed on XDA. When are you going to fully release it with a downloadable file?
Click to expand...
Click to collapse
There are sources, if u cannot live without compile it, I've written WIP
Not really a placeholder as source code is given.
Thanks!
linuxxxx said:
There are sources, if u cannot live without compile it, I've written WIP
Click to expand...
Click to collapse
justmpm said:
Not really a placeholder as source code is given.
Thanks!
Click to expand...
Click to collapse
Ah yes! My sincere apologies!
I was a bit too quick in judging, sorry. It's just that I am used to "Super Hax0r Skillaas Tools" placeholder threads, so I was expecting this to be one too.
Missed it
Will compile this evening, and report back if anything didn't work out for me.
Alpha released for unix and linuxamd64 (on Linux you may need qtwidget to make it start)
There are bugs and missing features!!
@ windows users: the code is (almost) ready, I just have to find a PC (or setup a VM) where I can compile and test this
Can u port this tools for Yu Yureka
ela1103 said:
Can u port this tools for Yu Yureka
Click to expand...
Click to collapse
Add a device support is pretty easy, so maybe
linuxxxx said:
Add a device support is pretty easy, so maybe
Click to expand...
Click to collapse
Waiting for the YU Yureka
Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
Finally, now xda can see some updates/threads for mipad
Kage Yume said:
Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
Click to expand...
Click to collapse
What a good news!. I Hope someone will already working in a newer ROM for Mi Pad ...
Hello,
This is a good news!!!
Hope some developers start playing with it.
Kind regards.
nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.
ChooiWC said:
nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.
Click to expand...
Click to collapse
I agree you.**** Off Xiaomi.
Sent using XDA One
The important question is.. how broken is it?
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.
Harrynowl said:
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.
Click to expand...
Click to collapse
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.
Based on which Android version? I'm hoping in a MIUI 8 based on Android Marshmallow for now, and future upgrade to Nougat. It will remain a dream?
Sudeep Duhoon said:
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.
Click to expand...
Click to collapse
Hello,
Is possible to build CM with this kernel?
Regards.
jlazkano said:
Hello,
Is possible to build CM with this kernel?
Regards.
Click to expand...
Click to collapse
Don't know. Never built rom.
In best of my knowledge, to build cm with this kernel, it would be difficult as we don't have device tree.
Android version upgrade is more difficult.
It boots with firmware blobs used in miui7. Works as well (nice change)
Harrynowl said:
It boots with firmware blobs used in miui7. Works as well (nice change)
Click to expand...
Click to collapse
Is this screenshoot a CM version of Mi Pad1?
Kind regards.
jlazkano said:
Is this screenshoot a CM version of Mi Pad1?
Kind regards.
Click to expand...
Click to collapse
Boots on CM11 also, if this is what you're asking
Harrynowl said:
Boots on CM11 also, if this is what you're asking
Click to expand...
Click to collapse
That is great!
If you upload the image, I could help testing it.
Best regards.
jlazkano said:
That is great!
If you upload the image, I could help testing it.
Best regards.
Click to expand...
Click to collapse
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC
Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
Yep. I too tried the same. I built CM13 from this kernel but not booting.
https://github.com/Nihhaar/android_kernel_xiaomi_mocha/
I know xiaomi source is broken.
Hi !
Harrynowl said:
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC
Click to expand...
Click to collapse
1. Could you explain whether this would allow use of the kernel with later versions of Android like Marshmallow or Nougat ?
2. If not, what would be required for it to work ?
3. As someone who is adept at compiling and editing kernels, could you recommend a few links related to compiling and editing kernels ? It would be of great help to new learners like myself.
Thanks !
Thank you !
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
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.
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 ??