I did all the process: unpack, change ramdisk to cloudy, repack and put into zip installer using my D802 I don't have pc, so here is the most far way to modified a kernel.
I use @somboons 30B stock bumped kernel & his bump script to made this un-important thing
You got nothing except newer build of stock kernel.
30B open:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/version
Linux version 3.4.0-perf-g88e404c ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Apr 16 22:21:38 IST 2015
[email protected]:/ #
CloudyG2 default:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/version
Linux version 3.4.0-perf-g2a934ab ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Apr 3 16:41:35 KST 2015
[email protected]:/ #
How to install: Flash from twrp.
Download:
30F stock for CloudyG2 3.x:
https://drive.google.com/file/d/0B3ue12JCB2NgRmszMlhhNWhNc3M/view
30B stock for CloudyG2 3.x:
https://drive.google.com/file/d/0B3ue12JCB2NgY1JwNzJHb2dBa2M/edit?usp=docslist_api
CloudyG2 3.1 default (original) kernel:
https://drive.google.com/file/d/0B3ue12JCB2Nga216bWlwZ0dod0E/edit?usp=docslist_api
Update:
1. I was thinking that the default kernel in Cloudy 3.1 was came from 30a open or 30d vdf (the first d802 LP build) but now I have sure that the default kernel (zImage) is came from 30e vdf so it's a new build too, only a few days older from 30b open.
2. I attach the script to create this mod if anyone curious howto modified a boot.img straight from the phone
3. Fixed the modules path. Thanks to @zioriky for the correction.
4. Both kernels tested works for Stock 30B.
Hi @didhiy
error on directory installation, system=>modules
exact system=>lib=>modules
zioriky said:
Hi @didhiy
error on directory installation, system=>modules
exact system=>lib=>modules
Click to expand...
Click to collapse
I just download the file & flash again to see anything wrong. Seems everything is ok to me.
I attach the last_log from my cache/recovery folder, maybe you can compare the results from your log to see what happens.
didhiy said:
I just download the file & flash again to see anything wrong. Seems everything is ok to me.
I attach the last_log from my cache/recovery folder, maybe you can compare the results from your log to see what happens.
Click to expand...
Click to collapse
The first download 30B stock for CloudyG2 3.1
This is the path to the zip system=>modules
The modules are in the lib folder?
zioriky said:
The first download 30B stock for CloudyG2 3.1
This is the path to the zip system=>modules
The modules are in the lib folder?
Click to expand...
Click to collapse
You're right :good: sorry, I put the modules in wrong path
Thanks for your correction. Will fix it later.
Edit: Done the fix. Seems using different modules from 30e on 30b or maybe others are compatible & worked. I still see a working texfat module when check "lsmod" from terminal emulator.
So how it goes? Flash the kernel 30B and then flash the fix, and the reboot?
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
So how it goes? Flash the kernel 30B and then flash the fix, and the reboot?
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
I fix the download link (remove the old one), just download and flash it & check the version from terminal emulator or hidden menu system info. Both are stock lp kernel with different build date.
What's the difference between the stock kernel and this one?
bouighil said:
What's the difference between the stock kernel and this one?
Click to expand...
Click to collapse
As stated in op, basically you got nothing except newer build date. Cloudy using 30e vdf zImage and I use 30b open. Both very similar just like you can install somboons bumped 30b kernel into his 30e vdf rom.
So it's useless? Not for me I already show a possibility to repack a kernel straight from my d802 for future experiments it's possible to use other custom zImage kernels like dorimanx repack with pure cloudy ramdisk. Of course the features of cortex brain script will lost, but still a nice experience for me to try
This would work withCloudy 3.2?
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
This would work withCloudy 3.2?
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
Yes, this works for cloudy 3.2 too. No kernel related was changed in Cloudy update.
Both kernels on op, tested works for Stock 30B too.
The explanation is simple, because both are stock zImage. The ramdisk part slightly changed by Cloudyfa, like removal of lg security check and set selinux permission to 0 (permissive).
Added newer stock kernel from 30f
https://drive.google.com/file/d/0B3ue12JCB2NgRmszMlhhNWhNc3M/view
The modules still came from 30b but everything should works fine.
I think this kernel should works on stock 30F rom with selinux set to permissive. Not tested yet...
Related
Hello !
Kernel-Build from source
Because I was able to build the Kernel from Huawei's source(3.0.8) for Huawei Ascend P6 ,
I want to open a Topic for Questions and Answers ! (like Surdu Petru did for his CM)
Post Questions and Ideas about this topic here :
Thanks !
regards,
raolleel
To build the kernel you need the source from huawei:
Chinese : http://download-c.huawei.com/download/downloadCenter?downloadId=16381&siteCode=cn (3.0.8) [B111]
International: http://download-c.huawei.com/download/downloadCenter?downloadId=17788&siteCode=worldwide) (3.08) [B111]
You also need the right toolchain : https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6
Little Tutorial to compile the kernel (Linux):
extract your source-file and your toolchain (only the 4.6 toolchain works)
open a terminal and cd into the source
now type:
export ARCH=arm (select architecture of your phone)
export SUBARCH=arm (select architecture of your phone)
export CROSS_COMPILE=[path to your toolchain]/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/arm-linux-androideabi- (tell the Kernel, where your compiler is)
make clean && make mrproper (to clean the source)
make hisi_k3v2oem1_defconfig ARCH=arm (to load the default config of your phone)
make menuconfig (configue the Kernel [dont change settings you don't know, or your kernel will not work)
make -j[number of your cpu-cores+1] ARCH=arm (This will start the process .. will take some time)
make ARCH=arm zImage
Click to expand...
Click to collapse
now you have your zImage of the kernel
raolleel said:
To build the kernel you need the source from huawei:
Chinese : http://download-c.huawei.com/download/downloadCenter?downloadId=16381&siteCode=cn (3.0.8) [B112]
International: http://consumer.huawei.com/en/support/downloads/index.htm?id=7583(3.0.8) [sorry site is not awaliable (i think huawei has some problems with its website)]
You also need the right toolchain : https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6 [B112]
Little Tutorial to compile the kernel (Linux):
extract your source-file and your toolchain (only the 4.6 toolchain works)
open a terminal and cd into the source
now type:
now you have your zImage of the kernel
Click to expand...
Click to collapse
International: http://download-c.huawei.com/download/downloadCenter?downloadId=17788&siteCode=worldwide
Kernel-Build-From-Source
Hi, I have compiled the International Kernel (3.0.8) and only added the compression to resize the Kernel a little bit.
Here is the zImage :
http://www.androidfilehost.com/?fid=23269279319201652
Btw. it is not tested (because my phone is in repair), only for devs
Its only a proof-of-concept
raolleel said:
Hello !
Kernel-Build from source
Because I was able to build the Kernel from Huawei's source(3.0.8) for Huawei Ascend P6 ,
I want to open a Topic for Questions and Answers ! (like Surdu Petru did for his CM)
Post Questions and Ideas about this topic here :
Thanks !
regards,
raolleel
Click to expand...
Click to collapse
So, can you build a custom kernel for this phone and we would get much better perfomance? Just asking.
BluntP6 said:
So, can you build a custom kernel for this phone and we would get much better perfomance? Just asking.
Click to expand...
Click to collapse
Much better .. not at this point ... but in the future ... maybee
I just started to get an idear how this phone really is ^^
At first, I was a little bit confused of the rom/kernel-history:
Code:
B107 International 4.2.2 -> 3.0.8-0769-g8cca155
B108 International 4.2.2 -> 3.0.8-0772-g83e47c3
B109SP02 International 4.2.2 -> 3.0.8-0779-g33784a0
B111 International 4.2.2 -> 3.0.8-0780-g62cb956
B112 International 4.2.2 -> 3.0.8-0780-g62cb956
B114 International 4.2.2 -> 3.0.8-0781-g88bfdc2
B118 International 4.2.2 -> 3.0.8-00788-g5d19ba2
B119 International 4.2.2 -> 3.0.8-00794-g8845b56
B125 International 4.2.2 -> 3.0.8-00795-g35bf84a
B109SP02 China 4.2.2 -> ?
B112SP01 China 4.2.2 -> ?
B115 China 4.2.2 -> 3.0.8-0802-g081004a
B116SP01 China 4.2.2 -> 3.0.8-00821-g6fd9b1d
B117SP01 China 4.2.2 -> 3.0.8-00829-gb6fffbf
B118 China 4.2.2 -> 3.0.8-00844
Everyone talks about that there are many different kernels, and that we only have the source of B111, but ... for me it sounds like there is only the kernel 3.0.8 (like we have the source) ... the code after the - is only a code to tell, when the kernel was builded/who builded the kernel
The Source is the Linux/Android-Kernel 3.0.8 (no subversion nothing added)
So a Kernel build with this source should work on every Firmware with the 3.0.8-kernel.
But we have another Problem.
To get the zImage working, you need the Boot.img ...
OK you can extract it via Huawei-Update-Extractor, but "abootimg" tells:
Code:
B111/BOOT.img: no Android Magic Value
B111/BOOT.img: not a valid Android Boot Image.
B118China/09.boot.img: no Android Magic Value
B118China/09.boot.img: not a valid Android Boot Image.
B125/09.boot.img: no Android Magic Value
B125/09.boot.img: not a valid Android Boot Image.
So at this point we can't put a zImage into boot.img because of wrong filesystem (I'll have a idear how to get out of this trouble, but I need some time)
Also there is a question, can't we simply flash 07.fastboot.img (from B118CH) over the B125International-Rom (to get the "bootloader unlocked")
We should be able to do this with dd, or am I wrong.
Some people told that they are able to flash the B125 without loosing the "unlocked-BL", so B125 must be able to boot.
Correct me if I'm wrong.
I'm only trying to get kernel-developing started ^^
I found a little Tool, by CNexus, which is able to extract and rebuild our boot.img
So I manged to make a boot.img (with slightly modified kernel) (B118CN)
My phone is in repair, so I need testers, but I want to say, this can brick your phone and I'm not responsible for this !
[DEV-ONLY] AOKP-Kernel 3.0.8 (International)
Untested AOSP-Kernel
Source:
Ascend P6 Open Source(P6-U06,JellyBean,kernel-3.0.8)
Click to expand...
Click to collapse
Features:
First Build
Only Added "Optimize for size" (so that the kernel should work without problems)
Click to expand...
Click to collapse
Credits:
m!k3 (for the right download-link ^^)
Huawei (for releasing this source)
CNexus (for his wonderful Boot.img tools)
worstenbrood (for his Huawei Update Extractor)
raolleel (Building the kernels)
Click to expand...
Click to collapse
Warning:
keep in mind : THIS IS NOT TESTED
tell me which bugs are there, or if this doesn't work
Only Works with Unlocked Bootloader, so you must have been on B118CN
Should work with B118CN
Should work with B125 if you were on B118Cn before
Could work with B111 if your Bootloader is not relocked when you flash B111 from B118CN
(only released because everyone said that the kernel is only for B111 [which I can't belive)
I am not responsible for bricking/destroying your phone. Custom kernels comes with no warranty.
Click to expand...
Click to collapse
Download (Testing-Build):
B111
B118CN
B125
Click to expand...
Click to collapse
A little Question/Conclusion
Huawei uses the same Kernel for CN and International Roms
So the orginal Kernel supports K3V2OEM1 Board and K3V2OEM2 Board
.. the kernel should be a little bit smaller if we remove one of this ...
so you get support for K3V2OEM1 (International ?)
or K3V2OEM2 (CN ?)
I tried Booting the B125 img, I'm on B118CN however the link for it leads to a 1.2MB file so based on previous kernel building experience I think the size is not right for a boot.img
Anyways, I tried with
Code:
fastboot boot boot.img
And failed to boot, the output was:
Code:
downloading 'boot.img'...
OKAY [ 0.233s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.236s
I didn't want to flash it straight to the phone, might give it a try to build a test kernel later on today and see how it goes as well.
Regards,
Jimbo
jimbo77 said:
I tried Booting the B125 img, I'm on B118CN however the link for it leads to a 1.2MB file so based on previous kernel building experience I think the size is not right for a boot.img
Anyways, I tried with
Code:
fastboot boot boot.img
And failed to boot, the output was:
Code:
downloading 'boot.img'...
OKAY [ 0.233s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.236s
I didn't want to flash it straight to the phone, might give it a try to build a test kernel later on today and see how it goes as well.
Regards,
Jimbo
Click to expand...
Click to collapse
Oh looks like androidfilehost is a ****ty hoster ^^
all boot.imgs are about 5MB
Yeap, the only one with a smaller size is the 118CN llink the other files are fine. Do you think it will make any difference to flash it to the phone (Using fastboot flash boot boot.img) instead of trying booting it from fastboot?
I uploaded all files to my Dropbox .. links are changed
It should work .. at least I hope it does
Its a testing-build .. and Huawei did many things with there source, which are ... not really intelligent ^^
Also the procedure to include the Kernel (zImage) to boot.img is untested, but I hope it will work
raolleel said:
I uploaded all files to my Dropbox .. links are changed
It should work .. at least I hope it does
Its a testing-build .. and Huawei did many things with there source, which are ... not really intelligent ^^
Also the procedure to include the Kernel (zImage) to boot.img is untested, but I hope it will work
Click to expand...
Click to collapse
Check your PM, i've sent you something we can try. Based on my experience with the S3, there was a script to generate the boot.img from within the phone using the existing ramdisk and a new Zimage. We might give it a try, also have you tried decompiling stock boot.img and see the contents of the ramdisk?
jimbo77 said:
Check your PM, i've sent you something we can try. Based on my experience with the S3, there was a script to generate the boot.img from within the phone using the existing ramdisk and a new Zimage. We might give it a try, also have you tried decompiling stock boot.img and see the contents of the ramdisk?
Click to expand...
Click to collapse
I extracted the Boot.img out of the three roms, unpacked it, and simply repacked it with the new zImage
.. But also, I can't work on my phone at this moment, its in repair .. (screen is not working like it should)
It works... I finally decided to use fastboot flash boot and it booted. Also the procedure I sent you via PM works too... I'll send you the zip file I used, probably it's a more user friendly way to update a kernel.
This is great, I'll soon start a kernel test as well. Been itching since I builded kernels for the 2011 Sony phones.
Good work!
Sent from my P6-U06 using Tapatalk
Cool .. that sounds nice .. then I can open a Tread in Orginal Android developing ^^
Again I am a little bit confused ..
the kernel-source of huawei has MHL-Support enabled by default ...
I thought the P6 doesn't have an MHL-option
I have no idea of kernels or github, but i see a huawei kernel 3.4 in there: https://github.com/Dazzozo/huawei-kernel-3.4
Dream come true ?
its not for k3v2....
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r27. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
2015/04/01
please visit http://forum.xda-developers.com/showpost.php?p=59827552&postcount=8 to see more information:
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108/.157 or any ROM based on it.
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
sharonliu said:
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r25. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108 or any ROM based on it
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
Click to expand...
Click to collapse
cocafe mentioned that the wifi modules has to be original from stock ROM, so i replaced them before flashing the kernel, but wifi does not turn on.
thank you for reporting this problem, it should be resolved next release.
Nice to see another stock based kernel around!
Only .108 or also .157?
Schlengge said:
Nice to see another stock based kernel around!
Only .108 or also .157?
Click to expand...
Click to collapse
from cocafe´s post:
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Click to expand...
Click to collapse
so imho for .157 too
sharonliu said:
thank you for reporting this problem, it should be resolved next release.
Click to expand...
Click to collapse
i think this solves the problem: LINK
moonryder said:
i think this solves the problem: LINK
Click to expand...
Click to collapse
Thanks for the information. Just like DooMKernel, my goal is no need to compile wlan module. If I am not luck, I will build the wlan module in this weekend.
Changelog :
wlan is working
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Insturaction:
If you want back to stock kernel, remember reboot to recovery and flash stock wife modules.
sharonliu said:
...flash stock wife modules.
Click to expand...
Click to collapse
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
moonryder said:
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
Click to expand...
Click to collapse
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
sharonliu said:
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
Click to expand...
Click to collapse
ok
btw flashed new build from today and wifi works like a charm.
thx
Thanks for this kernel
The only thing I noticed is that the notification light turns white when the battery is full
Normal it's green
Don't know if it's I bug but I noticed it
It's not a bug. Cocafe made it so the led will notify you of the real eoc. You can change the led color though here I believe "/sys/kernel/qpnp-charger/eoc_led"
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
moonryder said:
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
Click to expand...
Click to collapse
get terminal emulator from the play store and type it in there
or use adb shell
adb shell
su
Click to expand...
Click to collapse
it should work if you type these scripts. In my opinion, DoomKernel is the best custom kernel, bu nice to see another stock based kernel around.
sharonliu said:
...DoomKernel is the best custom kernel....
Click to expand...
Click to collapse
you are so right bro
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
a1b2c3901 said:
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
Click to expand...
Click to collapse
why do you use exFAT format?
Do you have files > 4GB in use?
moonryder said:
why do you use exFAT format?
Do you have files > 4GB in use?
Click to expand...
Click to collapse
Sometimes I will watch movie in the journeys, and that files may be oversize.
a1b2c3901 said:
Sometimes I will watch movie in the journeys, and that files may be oversize.
Click to expand...
Click to collapse
get "MLUSB Mounter" from the play store, you can use the USB hard drive (formatted NTFS, exFAT).
I managed to compile the kernel (http://forum.xda-developers.com/lg-g3/devs-only/compile-stock-lolipop-kernel-t3153006) but it won't boot, I am using the ramdisk that is using my current kernel (I'm on CloudyG3 2.5)
Any idea where to get a working kernel source? LG page kernel is the kernel that won't boot for some reason.. thanks
Feche said:
I managed to compile the kernel (http://forum.xda-developers.com/lg-g3/devs-only/compile-stock-lolipop-kernel-t3153006) but it won't boot, I am using the ramdisk that is using my current kernel (I'm on CloudyG3 2.5)
Any idea where to get a working kernel source? LG page kernel is the kernel that won't boot for some reason.. thanks
Click to expand...
Click to collapse
hey
is this stock or you add some features to it ?
there is a undefined function,
1-means new feature not implemented corectly
2-if its for D850 u should use proper defconfig for compilation, eg d855 is global so its "g3-global-... " and d851 is " g3-tmo- ... " - it's described in a readme file at downloaded zip file from lge.opensource
and why at this line "RGB LED synchronize in kddi" it's for f400 !!
3- which toolchain and compile command you using ?
4-if it's compiled, so use your variant's ramdisk,
Dualbootpatcher for P8000
We have official support for dualbootpatcher.
How does it work?
Install app and patch flashable zip. Install zip via recovery. Now you can switch between 2 or more Roms.
link
!! Use only matching kernel and bootloader !!
LP Bootloader = 3.10 kernel
MM Bootloader = 3.18 kernel
Do not mix 3.10 kernel and 3.18 kernel !!!
Download: link
Source: link
walter79 said:
Dualbootpatcher for P8000
We have official support for dualbootpatcher.
How does it work?
Install app and patch flashable zip. Install zip via recovery. Now you can switch between 2 or more Roms.
link
!! Use only matching kernel and bootloader !!
LP Bootloader = 3.10 kernel
MM Bootloader = 3.18 kernel
Do not mix 3.10 kernel and 3.18 kernel !!!
Download: link
Source: link
Click to expand...
Click to collapse
Thx for that! If I'm on aosp7.1.1 what rom could i install as second rom?
stock MM
does this elephone support internet over mhl / micro-usb to ethernet adapter?
@walter79 if i want to install these ported roms from russian 4pda forum:
XOS_v2_6.0_Elephone P8000 https://drive.google.com/uc?id=0BzQtiGXzY6RHbnRHamc3ek1EY0E&export=download
Vibe_3.5_Elephone P8000_6.0 https://drive.google.com/uc?id=0BzQtiGXzY6RHaXVRd2xqSHF2bHM&export=download
as multiboot or primary rom it won't work
Roms are for first revision and based on android 6 with kernel 3.18
Could it be that the partitions of these roms are different to 7.1.1 and twrp can't flash it?
please post fstab from this rom
thx for fast reply! here you have the fstab from each rom if you need something please let me know!
Thank you!
remove the "verify" flag
walter79 said:
remove the "verify" flag
Click to expand...
Click to collapse
so i have to unpack the ramdisk and remove the "verify" flag from /fstab.qcom? Or am i wrong?
Thank you and have a nice day!
Is it possible to get this to work for our device?https://forum.xda-developers.com/showthread.php?t=2491299 so we could backup each rom separately cause twrp backs up both roms together
@walter79 i removed the verify from this line in fstab:
dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait,verify
now it looks like this:
dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait
did you mean it like this? if so it still does not work for me i allways get the same error
walter79 said:
stock MM
Click to expand...
Click to collapse
do you have a flashable stock mm rom? my wont work
Note: I have only tested this on Mate 10 Pro, so I don't know if it works on Mate 10. Title will stay until tested
Kernel downloads: https://github.com/Ante0/BKL_OREO_EMUI8/tree/master/releases
Source used: https://github.com/Ante0/BKL_OREO_EMUI8
Currently upstreamed to: 4.4.130
4.4.60 and above contains Blu_Active governor
Windows: https://mega.nz/#!NTgEFKiZ!4nB6QuznpI-Q4R8mtJENZ34KV4YNr6aUIlMTyTYOQcQ
Download Kernel_Pack_tool_windows.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_windows folder, open a command prompt in the extracted folder and run "pack_kernel.bat 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
Linux: https://mega.nz/#!Ne5mXATT!FXjWsnY61VewihTWagrJ09G6jv15_y4BlS_R0HDQ5UM
Download Kernel_Pack_tool_linux.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_linux folder, open a terminal in the extracted folder and run "./pack_kernel.sh 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
If you get permission errors you may have to chmod +x pack_kernel.sh and mkbootimg
UPDATE: I have changed sources to use Honor View 10 instead as camera works here (and everything else) and I'm also upstreaming it. Currently at 4.4.52: https://github.com/Ante0/BKL_OREO_EMUI8.0
Downloads will come soon. I will make a new script to change patch level instead of changing each image (from 2017-12 to 2018-09) as it takes time and space on my mega.
This does not set selinux to permissive all the time, you have to use 'setenforce 0' to enable permissive, this is to only enable it when you need it.
All this does is let us use 'setenforce' again, since Huawei decided to disable it in Oreo.
Could be useful for V4A and other sound mods, since they usually require permissive. Or anything else that could need permissive.
V4A still doesnt work with permissive, something else needs fixing
Note: This is for Security Patch level 2018-01. If yours is 2017-12 or 2018-02 you will bootloop.
This is because --os_patch_level must match ro.build.version.security_patch in /vendor/build.prop
If so you need to repack kernel and change --os_patch_level to match your version.
I will keep my github updated with security patches from Google, but if Huawei changes something in their own source it won't be in this kernel.
Mate 10/Mate 10 Pro downloads: https://mega.nz/#F!FbBBCaIS!YYH94l12su3HcsbwIqDygg
(Check Settings -> About - "Android security patch:" to get the correct patch level.
If it says 1 January 2018, download and flash 201801 kernel. 1 February 2018: 201802 and so on.)
Flash using: Fastboot flash kernel kernel.img
Mate 10 Kernel source: https://github.com/Ante0/ALP_OREO_EMUI8
Mate 10 Pro Kernel source: https://github.com/Ante0/BLA_OREO_EMUI8.0
Update 10/2: Added Wireguard support, for those who like to use VPNs.
Added some simple build scripts
Please note that portrait mode in camera has been broken with custom kernel since BLA-L29C432B137
Not working on BLA-L09, error mode boot image load failed.
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
smariob said:
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
Click to expand...
Click to collapse
Bordo_Bereli51 said:
Not working on BLA-L09, error mode boot image load failed.
Click to expand...
Click to collapse
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
ante0 said:
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
Click to expand...
Click to collapse
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
@ante0
Thank you for the new kernel!!!
Keep up the good work dev :good::good::good:
smariob said:
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
Click to expand...
Click to collapse
No. Kernel is separate. Magisk goes in ramdisk.
Before oreo ramdisk and kernel was merged in the boot partition, but now they're split into ramdisk and kernel partitions.
So you only need to flash kernel to kernel.
Congrats for the first Mate 10 kernel, mate![emoji482]
noob question here: setenforce 0 is written in terminal or adb? how to?
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Bordo_Bereli51 said:
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Click to expand...
Click to collapse
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Saadkhalid786 said:
noob question here: setenforce 0 is written in terminal or adb? how to?
Click to expand...
Click to collapse
terminal.
Or use the Magisk Module as Bordo_Bereli51 suggested.
Though if you don't have any app or something that needs permissive it's no use in running it at all times.
ante0 said:
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Click to expand...
Click to collapse
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Bordo_Bereli51 said:
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
Click to expand...
Click to collapse
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
I am already doing that but wanted to know if he had stock but I am almost finished getting stock kernel
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
ante0 said:
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
Click to expand...
Click to collapse
Yes, looks like that driver is disabled, but i still didn't found another vibrator/motor.
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Bordo_Bereli51 said:
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Click to expand...
Click to collapse
It's set to always permissive.
Edit: And for me it bootloops for some reason.
ante0 said:
It's set to always permissive.
Click to expand...
Click to collapse
Which is why I want it in order to get V4A working
I am on kangvip rom.
Bordo_Bereli51 said:
Which is why I want it in order to get V4A working
Click to expand...
Click to collapse
I've tried with permissive, doesn't work with the Magisk Modules...
You might have luck with installing to /system and /vendor manually.
Kangvip might be why the kernel is not working for you, they usually incorporate their own hacks.