Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 3.18.100 and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/marlin
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
3.18.88 has been merged in.
3.18.89 has been merged in.
3.18.90 has been merged in.
3.18.91 has been merged in (conflict notes).
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
GeyerA said:
Hi Nathan, thanks for the code - built the kernel and flashed (wasn't easy at first). All working well, will use it at a later stage when I build the ROM. BTW, I am running the factory image. Credit also to Anykernel for the zip file
Click to expand...
Click to collapse
Not a Dev, but totally would like to give this a try if you have a zip. On the factory image + twrp 3.2.1
Sent from my [device_name] using XDA-Developers Legacy app
Hi, No problem. There you go... Just flash in TWRP and feedback if all went ok
3.18.92 has been merged in.
Hi, thanks for the code, compiled it against linaro 6.4 (built the cross-compiler following your thread). Tested for one day. All smooth. Sharing the job for those who might be interested. BTW, flashed it directly from fastboot....
Code:
fastboot flash kernel Image.lz4-dtb
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
No worries lol, gives it some life :silly:
Sent from my Pixel 2 XL using XDA Labs
GeyerA said:
Hi, added WireGuard support.
@ nathanchance, sorry, do not mean to hijack your thread...
Click to expand...
Click to collapse
Running this now, so far so good! Thanks!
Definitely interested in wire guard, but currently use WindScribe and am not sure how to properly configure it.
Will try and Frankenstein a config file together tonight and report back [emoji106]
Thanks again
Sent from my [device_name] using XDA-Developers Legacy app
Hi, question. Added DSPManager to my ROM and see that it always gets killed. Can you support the idea to build the kernel with
Code:
CONFIG_SECURITY_SELINUX=n
. Will this get me the kernel permissive and any disadvantages with this? I also see that Viper4android needs a permissive kernel.
3.18.93 has been merged in.
Somebody willing to do a build of the update to flash with fastboot?
I would if I could (still learning how to build myself)
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Somebody willing to do a build of the update to flash with fastboot?
I would if I could
Thnx in advance.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
jimbub said:
Was just going to ask if someone could point me to a good resource on how to do so. Will post anything I manage to do [emoji106]
Click to expand...
Click to collapse
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
I used this for the most part: https://forum.xda-developers.com/yureka/help/guide-compiling-64-bit-android-kernel-t3352728
And this:
https://forum.xda-developers.com/an...-how-to-compile-android-kernel-t3627297/page1
Was very helpful and am building right now
Credits to those guys offcourse.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Sgace said:
If it's ok, here is my personal first ever self built kernel from source. It's 3.18.93 and flashable in fastboot (unzip the zip and then: fastboot flash kernel Image.lz4-dtb)
Offcourse thnx to @nathanchance for the source and all the work!
Cheers
Click to expand...
Click to collapse
Thanks for doing this, very much appreciate it! For some reason though, this prevented my phone from booting. Ended up restoring my boot partition and things are well now!
Related
*Update 3/6/12*: I probably should have done this awhile ago, but I just wanted to clarify that this was a one-off release. It will not be updated since Nightlies/Weeklies are up and running again. In fact, they will have everything this ROM has plus more!
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
*edit* Dropbox mirror. Be gentle:
http://dl.dropbox.com/u/11998742/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Link not working for me mate...
Sent from my MB860 using XDA App
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Nice work,ghost_og.
I've used CM7.2 before on my Defy and Milestone 2. Many improvements over previous CM7. I'm waiting for multiupload link. Thanks for your hard work.
guidoido004 said:
Link not working for me mate...
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
NguyenHuu said:
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Click to expand...
Click to collapse
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
ghost_og said:
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
Click to expand...
Click to collapse
Thanks, will test it out, been looking for some updates to CM7.
The only nightly update you doesnt have is the ones specific for atrix....
You also could add tweaks and mods on it ^^
Flashing now, lets see how much good is it. Hehehe
Sent from my MB860 using XDA App
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
Click to expand...
Click to collapse
I think all of the fingerprint changes have been committed today, so you should get them if you pull the source to make your own build. No more splicing files necessary!
EDIT: Oops, I was wrong. Fingerprint branch was updated, but still need to merge those files into the base CM build.
the T9 dialer is great. Looking forward to more updates as more changes are comitted. Good work.
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
kennethpenn said:
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
Click to expand...
Click to collapse
Thank you! I appreciate it. Hehe, rapidshare...
ghost_og said:
Thank you! I appreciate it. Hehe, rapidshare...
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Have fun!
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
Click to expand...
Click to collapse
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Great news! I was debating whether or not to post this. I didn't want to step on any toes. Thanks for the hard work; I just synced and started a new build.
is it possible to flash this right over neutrino rom or is it best to full wipe?
Sent from my MB860 using XDA App
If coming from a cm7 based rom then just wipe /cache and dalvik. Been working for me switching between different versions.
Sent from my MB860 using XDA App
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=xHhUmRE2YOo
Can faux kernel be used with this rom?
Nipit said:
Can faux kernel be used with this rom?
Click to expand...
Click to collapse
Yes. The latest open beta runs very well for me.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Wow great news!! Will the Weekly #5 be based on CM7.2?
THIS THREAD IS WIP & FOR DEVELOPERS ONLY !
Technical information with sources & binaries is in post #2. It includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems with logs.
Click to expand...
Click to collapse
What is kexec?--------------------------------------------------------------------------------------------------------
kexec or kernel execution is a module/mechanism of the kernel that allows live/hot booting of a new/custom kernel "over" the currently running kernel. For more info, read the useful threads/links bellow.
kexec could be used to load a custom kernel into memory & yes, we'll then be able to install AOSP ROMs or in general run a custom kernel compatible with our device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updates:--------------------------------------------------------------------------------------------------------
[09/01/2014]:
kexec module has been successfully patched & loaded/inserted into both NC2 & NC4 stock kernels. Now, I'm working on compiling/loading a guest kernel & fixing possible problems/bugs.
Click to expand...
Click to collapse
[08/31/2014]:
Two versions of HLTEVZW KK kernel have been compiled from source: one uses the default configurations & the 2nd adds custom capabilities & kexec boot options. Moreover, kexec-tools & module have been cross-compiled. Now, I'm working on patches for kexec module & guest kernel (the hardest part).
Click to expand...
Click to collapse
[08/01/2014]:
I've successfully flashed a custom kernel on my device. This trips knox flag & isn't 100% related to kexec, but it has the same objective (loading custom kernel on the locked-bootloader devices). However, the bootloader makes security check & blocks the installed kernel with the "unauthorized software by VZW" warning. Then, I tried to patch the bootloader to remove this security check, but my device was HARD BRICKED. Now, I've created a General thread for how to recover from a HARD BRICK. This is promising info for testing bootloader exploits.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Status
--------------------------------------------------------------------------------------------------------
Supported NC2 & NC4 kernels
Working kexec-tools
Loaded kexec module
WIP kexec/guest kernel
Click to expand...
Click to collapse
Thanks to / Credits:
--------------------------------------------------------------------------------------------------------
@sextape - for the leaked NC2 firmware
@Hashcode - for his great work on kernel/recovery
...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
XDA:DevDB Information
KEXEC, Kernel for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr, CalcProgrammer1, ryanbg
Kernel Special Features:
Version Information
Status: Testing
Created 2014-07-11
Last Updated 2015-02-15
Technical Information
This post is reserved for technical information with sources & binaries. This includes kernel building, kexec-module, kexec-tools, hijack script, required patches & current problems.
Kernel Building:
--------------------------------------------------------------------------------------------------------
The first step for building working kexec-module & tools is to cross-compile the kernel from source with the correct configurations. I won't describe how to build a kernel from source, but you may find this thread very useful.
I've used two different sources for the NC4/NC2 HLTE_VZW KK kernels. The 1st one is a part of SM-N900V_NA_KK_Opensource.zip released by Samsung for N900V NC4 kernel while the 2nd is available on @Hashcode's Github profile with 3 branches: hltevzw-kk-nc2 branch is modified for N900V NC2 kernel + 15 commits for compiling kexec as a module & other kexec patches.
The instructions provided by Samsung to build the NC4 kernel are to update CROSS_COMPILE toolchain environment variable in the Makefile & build with the default configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig
make
However, I've patched the sources & used menuconfig interface to customize kernel configurations as follows:
Code:
export ARCH=arm
make VARIANT_DEFCONFIG=msm8974_sec_hlte_vzw_defconfig msm8974_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig menuconfig
make
(menuconfig is added in the second line)
The default output is the kernel image (arch/arm/boot/zImage) & modules (drivers/*/*.ko). The kexec-module(s) will be built if you patched the sources & configured it as a module.
You may then use dtbTool to generate device tree dt.img & mkbootimg to pack the kernel in boot.img.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Module:
--------------------------------------------------------------------------------------------------------
There're many different flavors of kexec-mod sources. @delewer in this thread uses a standalone kexec-mod source MOD'd for Sony Xperia Z1 to be cross-compiled against the precompiled kernel source while @Hashcode in his sources on Github patches the kernel source to cross-compile kexec-mod with the kernel. Some modules may or may not use/port the hardboot patches. The output for kexec module/drivers have different names (the standalone kexec-mod source generates kexec_load.ko & procfs_rw.ko while the kernel source patched by @Hashcode generates 3 modules: arm_kexec.ko, msm_kexec.ko & kexec.ko).
To test if the cross-compiled modules are loadable & have the correct kernel headers, use insmod in terminal emulator (or a safe point with terminal like Safestrap) to insert the module into the kernel (assuming you've kexec.ko in /system/lib/modules/):
Code:
insmod /system/lib/modules/kexec.ko
Then, use lsmod to list & show the status of loaded modules:
Code:
lsmod
Alternatively, you may check if system call of the kernel includes kexec functions using:
Code:
cat /proc/kallsyms | grep kexec
The kexec-modules I've compiled are loadable & have been successfully inserted into both NC4 & NC2 kernels.
I'm using my own sources for kexec-module based on others & I'll share the sources with binaries & modules after making some required tests.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kexec Tools:
--------------------------------------------------------------------------------------------------------
I'm using the latest version of kexec-tools from here (currently, kexec-tools-2.0.8.tar.gz) cross-compiled for arm with custom configurations. Three binaries are generated including kexec (directly boot into a new kernel) & kdump (display kernel trace data). For more info, check the manpage of each binary & kexec/kexec-tools manuals/guides.
To test your kexec-tools cross-compiled binaries for arm,
Code:
kexec --help
assuming that they're in your PATH (e.g., /system/xbin) with executable permissions (e.g., 755).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hijack Script:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Required Patches:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Current Problems/Logs:
--------------------------------------------------------------------------------------------------------
will be updated soon...
Click to expand...
Click to collapse
Sent from my SM-G900V using Tapatalk
jr_718 said:
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
amebiasis said:
My eyes about popped out the side of my head when I saw this! It says your in testing have you had any luck at all? Thank you thank you thank you BTW!
Click to expand...
Click to collapse
I've tested several binaries for the same kernel version, but none works for now. I'll compile from source & see. However, please keep this this thread for devs discussions only until we release working kexec & guest kernel.
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
bmwh0r3 said:
Trying to keep the n3 alive before the n4 arrives? Lol seriously though congrats and thank you. Hope you and the devs here the best of luck. We, the re owners, appreciate all you have done already for us.
Click to expand...
Click to collapse
Note 4 is useless until it gets root & custom ROMs. For me, it'll be better ONLY IF we can break its security & unlock bootloader!
What about surge & ryanbg and e.v.a. I been following them and they both have a good idea on how things work well I think they are good for the job
Just a thought I had when unlocking my spare RAZR hd, but the kernels on the Razr and my note 3 are 3.4.97 and 3.4.0. Is the exploit part of the kernel or is there a reason I'm a user and not a Dev? If it is, motopacalypse.apk is what unlocked my RAZR. I'm just trying to learn so please don't think I'm a moron. I just don't know the coding aspect of android at all.
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
tpike said:
Have you got an irc or hangout open for discussion?
Thanks for your efforts! !
Click to expand...
Click to collapse
There is #Galaxy-Note-3 on Freenode but it's really quiet in there most of the time.
Many forum lurkers like me have been anxiously waiting for this breakthrough! Don't give up! I also believe in donating to hardworking devs like you guys! Good luck...
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Feche said:
I was an owner of a Motorola Defy and the day that it got KEXEC I was so exited.. so good luck for you guys! Nothing is impossible. :victory:
Click to expand...
Click to collapse
Who was devs on kexec on defy?
ironfisted said:
Who was devs on kexec on defy?
Click to expand...
Click to collapse
Not sure
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Good luck! Lots of us are waiting for this!
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
Keep it up man, I understand the hard work involved in doing something like this, but it will definitely pay of in the end!!! Thank you for your hard work and dedication, you got a lot of people counting on you
Sent from my BajaRom "L" Themed Note 3
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I see. Let me know if you'd like to contribute to this thread. I'll update it soon with more details about the required patches & the preliminary results of my tests ––after releasing a new version of JasmineROM.
ryanbg said:
I've been working on kexec for a little while now with limited success. My biggest problem is the getting the 4 byte CRCs for the kernel symbols used by the kexec module. Same with a few other projects I'm working on. They compiled the NC2 kernel with MOD VERSION and CRC. I've compiled it from source, but there's so much work to be done my head is spinning.
Click to expand...
Click to collapse
I was told by a defy dev that we would have better luck contacting hp touch pad kernel devs. I guess their kernel is more like ours I guess. Idk. I never tried contacting dev from their yet
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
- HostZero
Click to expand...
Click to collapse
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Syncing sources up on my server now....
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Roger That!
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
@HostZero, @Nonta72, @RendyAK Check out this : http://build-box.msfjarvis.me:8080/job/cm-13-seedmtk/lastBuild/console
Don't mind the job name, I had planned this for the other variant but now it's for infinix. My suggestion would be to create a GitHub organization and add in everybody to it rather than one person having it on his personal account. And also, gimme a local manifest for the d5110
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Build Fail. ? Hmm I will submit device tree tommrow for infinix
HostZero said:
Build Fail. ? Hmm I will submit device tree tommrow for infinix
Click to expand...
Click to collapse
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
Great!
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Click to expand...
Click to collapse
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
RendyAK said:
I have an github account, here it is. https://github.com/Rendyindo/
Since i didnt have any ubuntu computer, so i only can help with some system files. Is it ok?
Click to expand...
Click to collapse
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
https://github.com/d5110-devs
Go there and accept the invitation, then go to your repository settings and select Transfer and transfer the vendor tree to this organization. @Nonta72, you have an invitation pending too. @RendyAK, I couldn't find you on GitHub so send any of us your GitHub username and we'll add you
About the fail, it doesn't matter, I have shell access to the server as well so I can debug it properly in case there's an issue.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
HostZero said:
@RendyAK , @Nonta72 and @MSF Jarvis are requested to come here.
I have started to work on cm-13.0 device and vendor tree, any body please download latest cm-13.0 source.
we are going to discuss in comments.
Raised som cm-13.0 blobs, few blobs missing on stock 6.0? any file missing do a merge request. libMali.so was based on cm-12.1 so, if you have libmali based on stock 6.0 please handover or do a merge request.
Vendor: https://github.com/HostZero/android_vendor_d5110_infinix/tree/cm-13.0
Device: Work progress
- HostZero
Click to expand...
Click to collapse
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Nonta72 said:
libMali.so is indeed missing. Unless the compiler compiles one; I'm not sure we can boot cm13 yet. cm12.1's one is probably not compatible (kind of).
And I'm really sorry. I've been very busy lately.
I pushed some updates on my github. Still have lot of work to do there.
Click to expand...
Click to collapse
Hmm anyways I have pushed the cm-13.0 device tree too I have upstremed as many files as possible.
https://github.com/d5110-devs
MSF Jarvis said:
It'd be nice if you can probably arrange to dual boot Ubuntu or something because all the files in vendor and device have file system permissions set and Windows tends to completely ruin those. Without Linux you can't even help with the system files
Click to expand...
Click to collapse
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
MSF Jarvis Seems to be compiling and i have ubuntu but.. my package is done! as tree and vendor are ready try to compile.
Here by OFFICIAL TWRP:
https://dl.twrp.me/d5110
RendyAK said:
Hmm, okay.. Gonna dual boot it, or use virtualbox.
Or can i use bash in win10, and install git there, i know apt-get and everthing in ubuntu works there.
Click to expand...
Click to collapse
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
git works, but filesystem permissions are an ext* FS thing, and Windows doesn't recognize ext3 and ext4 formatted partitions so permissions will still get borked. Only solution is a Linux distro.
Click to expand...
Click to collapse
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
RendyAK said:
Okay then..
Edit:
We have 3.18 too, is it makes cm13 more stable?
Click to expand...
Click to collapse
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
Kernel 3.18? Dunno what to do with it honestly, @HostZero has been handling the device tree till now. I'm just setting up builds at the moment.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
OMG! You guys could provide 3.18, I have used the 3.10 which has come with STOCK 6.0 if you guys can provide MSF will update it!
- HostZero
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
HostZero said:
I have not done any changes with tree I have upstreamed may files available to cm-13.0 from 12.1.
Click to expand...
Click to collapse
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
MSF Jarvis said:
I've re-created the device repo with original files from @Nonta72's device tree. Please don't kill commit histories and steal credits. Nonta did the base work and deserves the respect for that. You can delete your local device repo, clone the device repo from d5110-devs and make your changes. And please, please, use meaningful commit messages. You don't have to make a commit for every file you change and you don't need to add a fake file every f***in' time. Please take out the time to learn how to use git before you continue work on the device tree since I can't be cleaning up the mess you make of the commit messages each time.
Sent from my Pixel V1 using XDA Labs
Click to expand...
Click to collapse
WTF! I should do again. C'mon man... I ll do later mostly not now. I will send you tree.zip better you can push it. Because my push is failing.
Good day lads,
Disclaimer:
Code:
I don't know if you noticed a thread in the Q&A section that was closed by Matt. While I respect Matt's decision to close it, I find it a very relevant topic... The future of LineageOS for the P9 Lite. Please note that I do respect meticulous' wishes to charge for his work because I know how time consuming it is I wish to firmly express that I do not condone this mentality when it comes to Linux based operating systems.
I decided to make this thread with my little Dev knowledge in order to attract more devs who's willing to put in work on a stable device tree for free in spirit of community and for all to enjoy.
I do not have the Lineage source code at the moment but I will start downloading soon, I do know that I will need help and I encourage more devs/beginners to lend a hand for the benefit of us all.
Please, to begin, post links to relevant tarballs/links/downloads for development purposes, device tree and kernels, anything you've worked on so perhaps we can all work together.
Cheers
Sent from my HUAWEI VNS-L31 using Tapatalk
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Carlyle_f said:
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Ignore it's just a critic custom rom user....[emoji12]
Hipom said:
Ignore it's just a critic custom rom user....[emoji12]
Click to expand...
Click to collapse
My words are razor sharp but honest and realistic.
Sent from my VNS-L21 using Tapatalk
Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Open source does not mean free, period.
pilgrim011 said:
On xda, it does mean free, period. People that think that they should be paid for contributing here are not welcome on XDA.
Click to expand...
Click to collapse
you are totally right
Just finish already. If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Also it should be in QA SECTION.
You start xda dev thread when you have something made already. Not just with idea.
lsander said:
If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Click to expand...
Click to collapse
This disussions are undesired here. I know a board where you can discuss that. If you want, feel free to have a look at it. This little Board is very pleased about every enlivenment. Opened a thread over there.
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Updated kernel
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Avsky0 said:
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Click to expand...
Click to collapse
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
dady000 said:
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
Click to expand...
Click to collapse
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Avsky0 said:
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Click to expand...
Click to collapse
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
dady000 said:
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
Click to expand...
Click to collapse
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Avsky0 said:
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Click to expand...
Click to collapse
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
dady000 said:
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
Click to expand...
Click to collapse
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Avsky0 said:
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Click to expand...
Click to collapse
Yeah you're right. I just checked it and I am copying Image instead of Image.gz. Seems like it's only a 'cosmetic' issue because it runs anyways.
Great news guys, my sources now compile with latest Linaro toolchain. The kernel actually barely needed any fixes, but I'm not releasing anything prebuilt yet, since I have no idea what impact on stability my hacks might have.
Screenshot
ndroid1562 said:
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Click to expand...
Click to collapse
Perhaps reading through GitHub commits, checking the code and see whether or not you're really interested. If you're using a Linux distribution which I strongly advise, learn bash scripts first - it's easy and self explanatory and from there you will get basics of directories and calling up files.
Goodluck
Sent from my HUAWEI VNS-L31 using Tapatalk
After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the backport code here:
https://github.com/mifl/android_[LIST] [/LIST]kernel_xiaomi_tissot.
You can see the Xiaomi original code here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tissot-n-oss.
You can see the cm-14.1 code here:
https://github.com/mifl/android_kernel_xiaomi_tissot/tree/cm-14.1
Please: do not ask questions about Merges, Mods and Tweaks, because they will not be answered.
Greetings.
mifl said:
After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the code here:
https://github.com/mifl/android_
kernel_xiaomi_tissot.
Greetings.
Click to expand...
Click to collapse
Does it build? I tried both yours and xiaomis and had a ton of errors
sooti said:
Does it build? I tried both yours and xiaomis and had a ton of errors
Click to expand...
Click to collapse
Please compile the kernel correctly.
You can get a compilation script in the following branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/build.
The original Xiaomi kernel and my Backport compile correctly using this script.
Greetings.
mifl said:
Please compile the kernel correctly.
You can get a compilation script in the following branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/build.
The original Xiaomi kernel and my Backport compile correctly using this script.
Greetings.
Click to expand...
Click to collapse
Script didn't work for me but I was able to build with your latest commits, cheers
Good work, thanks
It can be a very immortal device with the help of XDA
Sent from my Mi A1 using XDA Labs
sooti said:
Script didn't work for me but I was able to build with your latest commits, cheers
Click to expand...
Click to collapse
You can get the compilation script and apply it to your kernel source with this patch:
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/build.patch
mifl said:
After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the backport code here:
https://github.com/mifl/android_[LIST] [/LIST]kernel_xiaomi_tissot.
You can see the Xiaomi original code here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tissot-n-oss.
Greetings.
Click to expand...
Click to collapse
Thank you very much! I appreciate your help.
@mifl kernel boots fine but can you point me to the needed commits for oreo? I can't seem to find the needed ones
sooti said:
@mifl kernel boots fine but can you point me to the needed commits for oreo? I can't seem to find the needed ones
Click to expand...
Click to collapse
The smartest thing, at the moment is to include all the commits that we can find from the caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for Mi A1.". This will make the developers of LineageOS and others able to use these sources, and also make it easier to make a port to the CAF branch for Android Oreo.
This work I am starting to do now and will be uploaded to the branch of my kernel: "develop". This branch will be updated using force push, to reduce the aforementioned commit.
Greetings.
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
any kernel made for stock (8.0) with some mods
eg enabled Qcomm fast charge battery tweaks cpu throttling
etc? looking forward to it thanks ?
Nice job there! :highfive:
And thank you Xiaomi, for making devs work more harder than what they should have.
Sent from my Redmi Note 4 using XDA Labs
@mifl Can we use your modified kernel source to build Lineage OS, or does it need some modifications?
---------- Post added at 07:03 AM ---------- Previous post was at 06:59 AM ----------
[/COLOR @mifl Can we use this kernel to build Lineage 14.1 or does it require some more edits?
mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
Ya those look like the same commits I tried... I have no problem getting the kernel to boot but the data is encrypted... What am I missing?
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
I'm still at the same place as before... the kernel boots find (did also before) but the data is encrypted... What am I missing?
Isn't the tissot kernel source already based off LA.UM.5.6.r1-04600-89xx.0? It's obviously based on LA.UM.5.6.r1 coz Android 7.1.2 msm8953_64. Don't let the comment on the squashed commit fool you otherwise.
Sorry guys xda wasn't working for me hence it's showing multiple posts. Mod please remove duplicate posts like this one
Duplicate
Sorry guys xda wasn't working for me hence it's showing multiple posts. Mod please remove duplicate posts like this one
bgos10 said:
Isn't the tissot kernel source already based off LA.UM.5.6.r1-04600-89xx.0? It's obviously based on LA.UM.5.6.r1 coz Android 7.1.2 msm8953_64. Don't let the comment on the squashed commit fool you otherwise.
Click to expand...
Click to collapse
Xiaomi destroyed commit history on the released source, by squashing even the tags used as the base over an older, LA.UM.5.3-06310-89xx.0, as a single "Xiaomi kernel changes for Mi A1." commit.
Probably you've to run git diff HEAD~1 at least once and see what it mostly changed.
Sent from my Redmi Note 4 using XDA Labs
@Uvneshkumar. The kernel is open source, you can use this like you want.
Greetings.