With the exception of a modified hardware/qcom/display for legacy support this is a straight compile of Codeaurora's 4.1.1 (M76XXUSNEKNLYA2515)
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/boot.img
http://threader.zapto.org/experimental/s7/codeaurora-4.1/102113/system.img.bz2
Unpack system.img.bz2
Flash with fastboot.
fastboot erase cache
fastboot erase userdata
fastboot flash boot boot.img
fastboot flash system.img
Not working:
Phone.
Bluetooth.
Sensors.
Wifi.
Working:
display
Kernel source:
https://github.com/threader/Huawei_S7_kernel_2.6.35
Hardware/qcom/display & devices/huawei/s7
http://threader.zapto.org/experimental/s7/codeaurora-4.1/sources-buildprefs/
Android sources:
https://github.com/threader/
Credits
Asturel, dzo. Thanks!
Boot image will boot asturels CM10 http://goo.im/devs/asturel
A boot image to boot asturels cm10.1 on 10x http://threader.zapto.org/experimental/s7/cm10.1/boot.img
Hi,
Went trough my old disks and uploaded everything i could find to https://mega.co.nz/#F!3wAQxDDL!2MgX7NmPBUIOVYP3zLYElw
Upper Folders:
* Original Firmware (Norway - Sweden - Brazil)
Norway = 103 Sweden = ? Brazil = 101-2 || Brazil boot image can be used with Norway rom, a 101 will loose its camera when presented with the wrong version kernel
Seemingly ancient Huawei update app, for updating 2.1 to 2.2. ( In Firmware Folder )
* Original Froyo and Emotion Kernel sources
Seemingly lost from Huawei's site. Could not find the 2.6.32 kernel last i checked let alone 2.6.28
* Broadcom bcm4329 sources
Original upload by Huawei, suggest downloading all and comparing. Remember there being a problem with either of the files
Dev folder:
* Device-huawei-s7 / Hardware-qcom-display-s7 ( Codeurora 4.1.x / CM 10 (?) / JB)
To be compiled against a "M76XXUSNEKNLYA2515" Codeurora 4.1.x / CM 10 (?) / JB)
* Kernels
Latest 2.6.32.61 from me, suggest using the original config instead of the mine.
Earlier release of 2.6.35.14 - Should be stable but suggest github - https://github.com/threader/Huawei_S7_kernel_2.6.35 - again use your config!
What i think is the original Huawei S7 kernel just fixed to compile.
Codeaurora msm-2.6.32 - which i suggest grabbing this amongst others, if you want to start from scratch with kernel-2.6.32-FROYO.tar.bz2
* Broadcom - bcm4329
Unknown status, suggest a thorough look and compare against original Huawei - bcm4329 release.
* Codeaurora 4.1.x ( 4.1.1 ) M76XXUSNEKNLYA2515
Latest two experimental builds i could find
Codeurora-4.1.x-s7-nov-6-2013 was actually the last 4.1.1 date i found in my build directory, this may be wrong, but i uploaded what sees to be the last build i did really, but it might require 21-10-2013 boot.img to work.
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
christi9503 said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
Please help!
christi9503 said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
One question. You have the bootloader unlock? you as unlock the bootloader? Sorry for my bad English and greetings from Mexico.
Enviado desde mi LG-P714 mediante Tapatalk
neutrondev said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
Which Rom are u BUILDING?
All guides are here -> http://forum.xda-developers.com/showthread.php?t=2073370
Hi ! Everyone who's ROM Developer . i can't boot my LineageOS 15.0 (build by myself) (kiwi = Honor 5X)
i've stucking selinux problems or recovery problems , but i don't know what's commit in kernel to fix it :crying:
Device Source
Device : https://github.com/CEIT-Lineage/android_device_huawei_kiwi/tree/lineage-15.0
Kernel : https://github.com/aphisitworachorch/android_kernel_huawei_kiwi
Since oppo has not released kernel source for oppo a37f or not responding at all.
Here is the Unofficial kernel source code for oppo a37f (15399) varient.
Currently only M (cm13.0) kernel is bootable. We aren't able to boot O (lineage-15.1) till now.
Oreo kernel booted (3-4-20)
Things which are working on M(cm13.0) :-
- booting
- Touchscreen
- Audio
- Calls
- Internet
- Mtp/usb
- Wifi/BT
- Brightness ( backlight)
- Adb
- etc
Things which aren't working or isn't fixed
- Camera/ LED flash
- Charging ( it shows charging but not supplying any power to battery)
- Some sensors (Gyroscope)
- etc
Special thanks to @Yashraj22. and developers of oppo a37f for testing and providing logs, since I don't own this device
Please help us fixing bugs and boot android O kernel, so that this device can taste the flavour of latest Android versions
Oreo kernel booted (3-4-20)
Kernel source :- https://github.com/sheikhshahnawaz41299/android_kernel_oppo_msm8916/tree/cm-13.0
reserved #1
?
Good Work Mate!
Good work but where can i find cm13 or lineage 15.1 rom for oppo a37f to test this kernel source?
please help....
Kernel GS android14 BETA 3
The Generic Kernel Image (GKI) project addresses kernel fragmentation by unifying the core kernel and moving SoC and board support out of the core kernel into loadable vendor modules. GKI also presents a stable Kernel Module Interface (KMI) for vendor modules, so modules and kernel can be updated independently.
The kernel AOSP common kernels (also known as the Android common kernels or ACKs) are downstream of kernel.org kernels and include patches of interest to the Android community that haven't been merged into mainline or Long Term Supported (LTS) kernels.
This kernel is full GKI builded in " gs-google " everything will get overwritten by flashing this ( kernel image.lz4 , dtbo vendor_boot.img , vendor_dlkm.img ) .
Features:
-- Compiled with prebuilt Google clang
-- Based on latest kernel sources gs raviole & Google common 13-5.10-lts & 13-5.10 [ 5.10.178 ]
-- enable advanced tcp , BBR2 as default
-- enable MGLRU by default
-- ssg: version S908BXXU3CWAI in default
-- vendor_boot : latest ramdisk oriole android 14 beta 3
-- DTB :
fixed mismerge dtb , disabled debug dtb & removed all prototype dts.
-- allow gpu governor to use 848mhz. ( its not OC its pre-enabled by google ! )
-- removed sound codecs not used on raviole / removed excessive debugging config
-- Simple Low memory killer for kernel 5.10 ( by Sultanxda )
-- removed PMU poll features in pixel_sched governor ( patch by Sultanxda adapted for A14 sources )
-powerhint module added for adjust PMU change
--added cpumasks for big, LITTLE, and prime CPU clusters in kernel source
--Use SCHED_RR in place of SCHED_FIFO / use kthread SCHED_RR in pixel_sched governor
-- fixed some spam log
Requirements
-Before flashing, you must first backup your stock boot.img. If you encounter any bootloop, you can always restore the system by flashing back to the stock factory boot using fastboot.
- the kernel is made for devices oriole & raven Android 14 beta2
- unlocked Bootloader required
if you have no disabled verity/verification and you re-flash stock boot , you need reflash stock vbmeta.img or you will get corruption be carefull
How to flash the Kernel:
1 Make sure you tick all the requirements above
1. Download the kernel.zip
2. Flash the kernel.zip via kernel flasher. Root will be preserved.
3. Reboot and profit.
About bugs and reports:
don't bother to post if a log isn't ready or without steps so the behavior can be replicated.
I only active support stock ROM android 14 beta 2.1 with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc... flashed in android 13 ...
kernel is tested from my device pixel 6 [oriole ] .
Download:Download kernel here
kernel version : 5.10
Sources : GITHUB
Group support : https://t.me/gs_kernelraviole
07/06/2023
! ONLY RAVIOLE ANDROID 14 BETA 3
change :
-- vendor_boot : latest ramdisk oriole android 14 beta 3
-- Merged google modules beta3 change
-- DTB :
fixed mismerge dtb , disabled debug dtb & removed all prototype dts.
allow gpu governor to use 848mhz. ( its not OC its pre-enabled by google ! )
--removed sound codecs not used on raviole / removed excessive debugging config
-- fixed some spam log
-- Simple Low memory killer for kernel 5.10 ( by Sultanxda )
-- removed PMU poll features in pixel_sched governor ( patch by Sultanxda adapted for A14 sources )
-powerhint magisk module added for adjust PMU change
--added cpumasks for big, LITTLE, and prime CPU clusters in kernel source
--Use SCHED_RR in place of SCHED_FIFO / use kthread SCHED_RR in pixel_sched governor
for full change see commit in sources.
27/05/2023
! ONLY RAVIOLE ANDROID BETA 2.1
now everything will get overwritten in flash ( kernel image.lz4 , dtbo , vendor_boot.img , vendor_dlkm.img ) .
--added backport cpuidle teo : util-awareness in sched_pixel governor
-- add toggle for disabling newly added USB devices
-- vendor_boot : latest ramdisk oriole android 14 beta 2.1
-- fixed mismerge dtb , disabled debug dtb
-- removed sound codecs not used on raviole.
25/05/2023
-- latest kernel sources Google common 13-5.10-lts [ 5.10.178 ]
-- ssg: version S908BXXU3CWAI
EDIT 26/05 : rebuilded - included latest 5.10 branch over 5.10-lts for fix bootlop in android 14 beta 2.1
LineageOS work, battery lasts better than stock. Thanks for your work
fk4mil said:
LineageOS work, battery lasts better than stock. Thanks for your work
Click to expand...
Click to collapse
Thanks for review )
I am a novice, how to compile the kernel of Pixel6
This did not work for me on Evolution X with Franco Kernel Manager or Kernel Flasher same story with three other kernels so maybe I'm doing something wrong?
k9r4n16 said:
This did not work for me on Evolution X with Franco Kernel Manager or Kernel Flasher same story with three other kernels so maybe I'm doing something wrong?
Click to expand...
Click to collapse
Dm Verity is disabled ? I see gki kernel require dm verity disabled in log ( bootloop - ERROR_VERIFICATION avb )
extract the vbmeta.img from the matching factory image and flash it in fastboot via:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Warning Its require full wipe!
k9r4n16 said:
This did not work for me on Evolution X with Franco Kernel Manager or Kernel Flasher same story with three other kernels so maybe I'm doing something wrong?
Click to expand...
Click to collapse
And make sure before flash stock img dtbo ,vendor_boot , vendor_dlkm,boot
debug_cat said:
I am a novice, how to compile the kernel of Pixel6
Click to expand...
Click to collapse
Building Kernels | Android Open Source Project
source.android.com
UPDATE KERNEL
-- latest kernel sources Google common 13-5.10-lts merged into 13-5.10 [ 5.10.178 ]
-- ssg: version S908BXXU3CWAI
*Note : kernel is compatible for android 14 beta 2 but if you have bug verify its kernel before starting spamming ...
EDIT 26/05 : rebuilded - included latest 5.10 branch over 5.10-lts for fix bootlop in android 14 beta 2.1
UPDATE KERNEL
! ONLY RAVIOLE ANDROID BETA 2.1
now everything will get overwritten in flash ( kernel image.lz4 , dtbo , vendor_boot.img , vendor_dlkm.img ) .
--added backport cpuidle teo : util-awareness in sched_pixel governor
-- add toggle for disabling newly added USB devices
-- vendor_boot : latest ramdisk oriole android 14 beta 2.1
-- fixed mismerge dtb , disabled debug dtb
-- removed sound codecs not used on raviole.
ada12 said:
UPDATE KERNEL
! ONLY RAVIOLE ANDROID BETA 2.1
now everything will get overwritten in flash ( kernel image.lz4 , dtbo , vendor_boot.img , vendor_dlkm.img ) .
--added backport cpuidle teo : util-awareness in sched_pixel governor
-- add toggle for disabling newly added USB devices
-- vendor_boot : latest ramdisk oriole android 14 beta 2.1
-- fixed mismerge dtb , disabled debug dtb
-- removed sound codecs not used on raviole.
Click to expand...
Click to collapse
Thank you! It seems much smoother than before. I try it and will report.
Kernel is very battery friendly and smooth on the Oriole with Beta 2.1.
I only noticed 2 things:
Some messages are delayed in stand by. But I believe this is a Android 14 thing....
The other: If I start the camera with double press power after a long stand by time, sometimes the screen is blank for 2-3 seconds. After this seconds the cam working normally.
In stock kernel it works directly.
Seosam said:
Kernel is very battery friendly and smooth on the Oriole with Beta 2.1.
I only noticed 2 things:
Some messages are delayed in stand by. But I believe this is a Android 14 thing....
The other: If I start the camera with double press power after a long stand by time, sometimes the screen is blank for 2-3 seconds. After this seconds the cam working normally.
In stock kernel it works directly.
Click to expand...
Click to collapse
about screen blank for 2-3 seconds you are sure its never happen in stock kernel ? actually in test in my device I no see it but they are many report about camera issue in tracker android...
here a big list of report https://issuetracker.google.com/issues?q=camera
you could give me log ... but I really cant warranty I can doing anything its very probably random issue of beta android.
ada12 said:
Building Kernels | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thank you. I have successfully compiled and burned the kernel onto the device
ada12 said:
about screen blank for 2-3 seconds you are sure its never happen in stock kernel ? actually in test in my device I no see it but they are many report about camera issue in tracker android...
here a big list of report https://issuetracker.google.com/issues?q=camera
you could give me log ... but I really cant warranty I can doing anything its very probably random issue of beta android.
Click to expand...
Click to collapse
I can live with it, so I'll wait for Beta 3
UPDATE KERNEL
! ONLY RAVIOLE ANDROID 14 BETA 3
change :
-- vendor_boot : latest ramdisk oriole android 14 beta 3
-- Merged google modules beta3 change
-- DTB :
fixed mismerge dtb , disabled debug dtb & removed all prototype dts.
allow gpu governor to use 848mhz. ( its not OC its pre-enabled by google ! )
--removed sound codecs not used on raviole / removed excessive debugging config
-- fixed some spam log
-- Simple Low memory killer for kernel 5.10 ( by Sultanxda )
-- removed PMU poll features in pixel_sched governor ( patch by Sultanxda adapted for A14 sources )
-powerhint magisk module added for adjust PMU change
--added cpumasks for big, LITTLE, and prime CPU clusters in kernel source
--Use SCHED_RR in place of SCHED_FIFO / use kthread SCHED_RR in pixel_sched governor
for full change see commit in sources.
Never thought to check the PIXEL 6 forum...I own the raven. Have been on 14B3 for a few days and just flashed this kernel.
YOU
HAVE
SOLVED
ALL
MY
PROBLEMS.
I was like I really need a custom kernel but no one builds for 14. This is it. My phone is SO smooth now. Thank you thank you thank you!