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).
Related
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
https://github.com/untermensch/asus_kernels
getting started with building kernels:
http://source.android.com/source/building-kernels.html
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
update 11-21-2012:
add cifs, md4 modules
update 10-27-2012:
add data2sd support
uncap sd card DTR
add DUB-E100 revision C dev id
update 10-11-2012:
add zram support
add zram swap
add init.d
add OC kernel for the TF300TL, TF300TG
update 10-05-2012:
fix exFat mounting
revert MosChip MCS7830 driver
update 10-04-2012:
NTFS R/W via ntfs-3g
noauto_da_alloc added to fstab.cardhu
updated MosChip MCS7830 driver
added GPU overclock to 520Mhz from Motly-git
added user voltage control from Motly-git
possible I/O latency tweek
update 10-02-2012:
NTFS mount fail fixed (read only)
all I/O scheduler's included
support for MosChip MCS7830 based Ethernet adapters added
attached is the current snapshot of the repository.
changes:
debug stuff removed
OC to 1.6GHz
simple I/O scheduler as default
pegasuq governor added
zcache and cleancache enabled
CWM flash-able
Great move... lets see if someone dedicates some time to this wonderful gadget
Sent from Chanook 300 using Tapatalk 2
I'm running the source built kernel now and it appears that all the devices work
you may want to start a dev.. go ahead
untermensch said:
I'm running the source built kernel now and it appears that all the devices work
Click to expand...
Click to collapse
Hi !
..also I compiled the 10.4.2.9 kernel source code , and seems to be stable and no issue !
:good:
I have somme issue with dock keyboard ...as soon as it is connected = frequent reboot in any JB rom ( stock or custom !)
I hope this latest update 10.4.2.13 to resolve this ! :good:
untermensch said:
https://github.com/untermensch/tf300t_kernel
I started with the source from the ASUS website and the Linux 3.1.10 source from
kernel.org and made a some patches for the various directories, created a new git
repository and made a commit after each patch is applied to the Linux 3.1.10
kernel source tree. So now you can browse the changes made to the Linux 3.1.10
source to make it into a kernel for the TF300T.
Click to expand...
Click to collapse
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Valantur said:
Thanks for your work.
Could you tell me why would be beneficial to port Linux 3.1.10 to the TF300?
Click to expand...
Click to collapse
the official ASUS kernel source is based on 3.1.10 so I am not porting anything, I am using
github to display the differences between the source released by ASUS and the base Linux
3.1.10 source it was built from. I do believe that the repository would be helpful to port to
a newer kernel, after the patches have been applied it is basically the ASUS source, but I
did fix a few things so it would build.
applied patch for the 10.4.2.13 kernel source
untermensch said:
applied patch for the 10.4.2.13 kernel source
Click to expand...
Click to collapse
Good .. that should fix the reboot issue which afaik occurs if you have a SD inserted in the dock
Sent using The Beast via Tapatalk 2
CPU over clocking to 1.6Ghz pushed to the repository
add
Code:
CONFIG_TEGRA_OC=y
to your .config
and remove
Code:
CONFIG_TEGRA_EDP_EXACT_FREQ=y
from your .config
or make xconfig and tick the TF300T Over Clocking check box
well that is nice. Can you post your OC Kernel for us?
mikaole said:
well that is nice. Can you post your OC Kernel for us?
Click to expand...
Click to collapse
here is the kernel plus the modules that go into /system/lib/modules
see this post for install instructions
http://forum.xda-developers.com/showpost.php?p=31944448&postcount=34
Thx, but Kernel is not flashable
untermensch said:
here is the kernel plus the modules that go into /system/lib/modules
Click to expand...
Click to collapse
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
normally you just flash the kernel in Recovery and you can copy the modules with root explorer. But flashing the Kernel fails in TWRP.
nothing I do will ever be "flashable" because people are stupid and will flash anything on to
any device.
install the kernel vi fastboot
Code:
fastboot flash boot kernel.blob
modules are optional install via adb while in recovery
Code:
adb shell sh -c "rm -fr /system/lib/modules/*"
then cd into the directory with the modules
Code:
adb push ./ /system/lib/modules
stevtec86 said:
This files, are compatible on Fw asus JB 10.4.2.13 with root, insecure kernel + busybox?
and how to instals the two files?
Thank's for reply and thank's for greats works
Click to expand...
Click to collapse
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
thx, just saw the blob myself. Its already done
Works fine here. Big THX
untermensch said:
this is a 10.4.2.13 kernel, the ram disk is stock. I'm sure if you request it
the dev for your kernel will merge the overclocking changes so you can
have OC to.
Click to expand...
Click to collapse
Two other questions:
1 - I have the TERP recovery, is that a problem?
2 - OC frequencies can be selected?
1. no problem at all, have TWRP, too
2- Yes can be selected in the OC app like set CPU or Antutu Master
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Sony Xperia Z1 (honami)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Big credits to @DooMLoRD for his help to rebase on stock kernel
XDA:DevDB Information
[honami][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia Z1
Contributors
Phil3759, DooMLoRD, [NUT]
Version Information
Status: Testing
Created 2014-03-29
Last Updated 2014-03-29
hello and thank you.
I have found the file. img I can not find my method for installing or flashed to the files on my Z1.
sorry i use google translation I'm French
Français
bonjour et merci . j'ai bien trouvé le fichier .img mes je ne trouve pas la méthode pour l installer ni pour flashé le fichiers sur mon Z1
Bien cordialement
Xque_31
Envoyé de mon C6903 en utilisant Tapatalk
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
hi @Phil3759,
firstly welcome to the Z1 forums!
the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:
http://forum.xda-developers.com/showthread.php?t=2447310
I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..
download link for fixed image is:
http://d-h.st/Iz2
BTW me and my colleague @Napstar have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):
our sources have also been released quite some time back:
http://forum.xda-developers.com/showthread.php?t=1485829
but i discontinued work on it as i got busy with personal work
I would recommend getting in touch with @Napstar, may be we can collaborate for some bigger things
also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel? (I have made my DooMKernel for close to 21 devices from various vendors Sony, HTC, Samsung, Huawei, Kindle, etc; currently I actively support only 4 devices though: Xperia Z1, Z, SP & T)
note to users:
if you want to test out this recovery then you need to HOTBOOT this kernel:
Code:
fastboot boot kernel.img
regards,
DooMLoRD
DooMLoRD said:
hi @Phil3759,
firstly welcome to the Z1 forums!
the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:
http://forum.xda-developers.com/showthread.php?t=2447310
I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..
download link for fixed image is:
http://d-h.st/Iz2
BTW me and my colleague @Napstar have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):
our sources have also been released quite some time back:
http://forum.xda-developers.com/showthread.php?t=1485829
but i discontinued work on it as i got busy with personal work
I would recommend getting in touch with @Napstar, may be we can collaborate for some bigger things
also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel?
note to users:
if you want to test out this recovery then you need to HOTBOOT this kernel:
Code:
fastboot boot kernel.img
regards,
DooMLoRD
Click to expand...
Click to collapse
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Phil3759 said:
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Click to expand...
Click to collapse
well @Napstar is currently working on something new please get in touch with him, he is busy with his PhD work but I am sure he can find out some time
it wont even boot on any Z1 irrespective of ROM... actually the kernel formats for Sony devices vary A LOT! they are not using standard boot.img format... and anyways especially for the msm8974 board (and beyond) the new device tree format will be used... its a bit tricky to explain but Krab has a good tutorial here:
http://forum.xda-developers.com/showthread.php?t=2469421
sure go ahead... u can link the recovery.img where ever u want i just repacked ur ramdisk with the correct zImage & dt.img
Phil3759 said:
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Click to expand...
Click to collapse
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
DooMLoRD said:
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
Click to expand...
Click to collapse
That's a lot
I will take a look at it or maybe just provide recovery.zip installer so that interested devs can repack, or even the ramdisk
Huge thanks
I will get in touch with Napster :good:
DooMLoRD said:
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
Click to expand...
Click to collapse
I took a look at your script
I was aware of the dt.img and already use it for Note 3 and Note 10.1 2014 from Samsung and on many of the new LG devices
Actually, cm-11.0 build tree is fixed to use a custom bootimg make file:
https://github.com/CyanogenMod/android_device_sony_rhine-common/blob/cm-11.0/custombootimg.mk#L56
The dt.img is kernel specific and is built along the zImage as you surely know. When compiling cm-11.0 boot.img, the zImage and matching dt.img are compiled and repacked using custombootimg.mk
Unpacking your fixed recovery.img I see the only changes are the dt.img and zImage to be able to use with stock ROMs. That's great and most people would prefer it that way
However, I am still unsure why you say that my original release won't boot a cm-11.0 ROM? Is it mandatory to have the kernel built along the ROM ? I do not think else your repack with zImage would work only on one specific ROM
Hope you can enlighten me on that
Phil3759 said:
I took a look at your script
I was aware of the dt.img and already use it for Note 3 and Note 10.1 2014 from Samsung and on many of the new LG devices
Actually, cm-11.0 build tree is fixed to use a custom bootimg make file:
https://github.com/CyanogenMod/android_device_sony_rhine-common/blob/cm-11.0/custombootimg.mk#L56
The dt.img is kernel specific and is built along the zImage as you surely know. When compiling cm-11.0 boot.img, the zImage and matching dt.img are compiled and repacked using custombootimg.mk
Unpacking your fixed recovery.img I see the only changes are the dt.img and zImage to be able to use with stock ROMs. That's great and most people would prefer it that way
However, I am still unsure why you say that my original release won't boot a cm-11.0 ROM? Is it mandatory to have the kernel built along the ROM ? I do not think else your repack with zImage would work only on one specific ROM
Hope you can enlighten me on that
Click to expand...
Click to collapse
the original boot.img didnt have a dt.img
DooMLoRD said:
the original boot.img didnt have a dt.img
Click to expand...
Click to collapse
really wired as I used the device tree with custom bootimg make file I linked above
I will look at it and thank you for your repack. I added to main goo.im repo
Afternoon chaps,
Just wanted to give this a whirl as i've used your recoveries before, so out of the two which are on the download section, which one should work on 4.2.2, with a locked bootloader?
Cheers m8 an glad you've made it onto the Z1
@Phil3759
For some reason on locked bootloader devices, while the texfat module has been loaded, I'm unable to get philz touch to mount any exFAT sdcard unless I change the extra.fstab line for it from 'auto' to 'texfat' ... any way to get this working normal again?
[NUT] said:
@Phil3759
For some reason on locked bootloader devices, while the texfat module has been loaded, I'm unable to get philz touch to mount any exFAT sdcard unless I change the extra.fstab line for it from 'auto' to 'texfat' ... any way to get this working normal again?
Click to expand...
Click to collapse
The honami version is compiled without minivold support for exfat modules. It will only work with fuse
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L520
You can try to use the yuga minivold binary instead. If it is ok and you want to add support it officially with updates, I will do like yuga and enable the exfat flag
hey I have the Xperia T & SP can you create a touch version for them too?
i can be your guinea pig for testing
SP: https://github.com/CyanogenMod/android_device_sony_huashan
T: https://github.com/CyanogenMod/android_device_sony_mint
DooMLoRD said:
hey I have the Xperia T & SP can you create a touch version for them too?
i can be your guinea pig for testing
SP: https://github.com/CyanogenMod/android_device_sony_huashan
T: https://github.com/CyanogenMod/android_device_sony_mint
Click to expand...
Click to collapse
Compiled and opened dedicated threads
Feel free to put your magic if needed :angel:
@Phil3759: The backlight is really very dim on locked bootloader devices... setting that to the max setting doesn't change it all that much either.
Anything I can do to test if it's philz touch causing this?
[NUT] said:
@Phil3759: The backlight is really very dim on locked bootloader devices... setting that to the max setting doesn't change it all that much either.
Anything I can do to test if it's philz touch causing this?
Click to expand...
Click to collapse
I use this path:
Code:
/sys/class/leds/wled:backlight/brightness
Since the repack was done using a stock kernel, not sure if it still matches!
Phil3759 said:
I use this path:
Code:
/sys/class/leds/wled:backlight/brightness
Since the repack was done using a stock kernel, not sure if it still matches!
Click to expand...
Click to collapse
It does still match. It's like the value to it got cut in half...
[NUT] said:
It does still match. It's like the value to it got cut in half...
Click to expand...
Click to collapse
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Phil3759 said:
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Click to expand...
Click to collapse
Busy with making a system dump on my Z1 now, will do that soon though.
---------- Post added at 12:55 AM ---------- Previous post was at 12:36 AM ----------
Phil3759 said:
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Click to expand...
Click to collapse
[NUT] said:
Busy with making a system dump on my Z1 now, will do that soon though.
Click to expand...
Click to collapse
Done that:
Code:
~ # cat "/sys/class/leds/wled:backlight/brightness"
10
~ # cat "/sys/class/leds/wled:backlight/brightness"
255
First one is from the screen/power save mode, the second is when fully lit... but still the screen is only half as bright or maybe even less then half compared to using the XZ philz ...
if cm11 out i will buy one
Sent from my Moto G using Tapatalk
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Riyal said:
I'm currently working on unofficial build CM10.2.
Kernel is done
device tree is done
vendor setup is done
Android sources currently downloading
testing not yet.
Click to expand...
Click to collapse
Not CM11, but still very exciting =)
TheQwertiest said:
Not CM11, but still very exciting =)
Click to expand...
Click to collapse
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Riyal said:
I will try cm11 once i get cm10 running. Thing is we don't have official android 4.4 roms yet I don't have any sources for 4.4 binaries and kernel
Click to expand...
Click to collapse
We wait for CM11!
Xperia V, T doesn't have official 4.4 ROM too, but they have CM11.
Also, I think it's possibile developing CM11 or other CM11 based (KitKat) AOSP ROM.
Unfortunatelly I can't develop it...
I just will use it :fingers-crossed:
u guyz are lucky...u have munjeni wid u now. just be patient.. his hardwork brought cm11 novathor devices... which were abondoned on ics.
two reason i see z1compact as my next phone is that i dont like large phones and master munjeni has z1c also...
We can use CM11 from Z1 since Z1 CM11 on Z1C is working but there is no display available since CM kernel on MSM8974 need some changes related to the Z1C display Bad news is we can not use stock kernel since gralloc, copybit ..etc is not working than. I started working on CM kernel but hmmm CM kernel and stock kernel is a lot diferent so hard work is needed If we get CM kernel working we will get CM11 working with no big modifications
Edit:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded https://github.com/CyanogenMod/android_kernel_sony_msm8974 branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Can't wait to try CM
kernel config from boot.img
munjeni said:
Compared now stock Sony kernel source code from Z1 and stock ekrnel source code from Z1C, there is absolutly no diferencie, only one line is diferent in defconfig, line is CONFIG_MACH_SONY_*****_ROW, source is totaly identic. I'm confused now since have no idea why CM kernel working on Z1 but no on Z1C. Maybe I have downloaded wrong kernel for Z1 ??? I have downloaded{removed} branch cm-11.0 . Maybe these kernel not working on Z1 too ???
Click to expand...
Click to collapse
Hello,
I am not sure if this is helpfull, but I'll give it a try: You are right - there is absolut no difference between the two kernel configurations, beside that one line. Since there are already nightlies available for the Z1(honami) I thought there might some helpfull informations inside that nightly. Of course there was a boot.img inside the nightly and I found that script to extract the kernel.config from that boot.img. Using the extract-ikconfig from my xperia z(yuga) kernel located in ./kernel/sony/apq8064/scripts/extract-ikconfig.
If the extracted config is reliable, there are indeed many differences.
I attached the extracted config. Maybe you remove the Lines starting with # and the blank lines for a better compare.
Let me know if I can help in some way.
Kind Regards
I don't know whats going on or why CM kernel is working on Z1 and not on Z1C but I think these fails on Z1C is related to the baseband and bootloader? Just asking, DO NOT FLASH THEM!!!
And another thing is maybe dtbs is a thing related to the fail since I can see some things in dmesg related to the pingpong command in mdss_mdp_intf_cmd.
Error log -> http://pastebin.com/9zgcWd4a
Thanks to the developers who are trying to make CM11 working on this phone. I will buy this phone if CM11 is available
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Riyal said:
@munjeni
Guys I have compiled a CM10.2 kernel here. Who's willing to try it against Z1's CM10.2 ROM?
http://forum.xda-developers.com/showthread.php?t=2461282
I'll provide the source if it works.
Click to expand...
Click to collapse
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Nope, doesn't seem to boot :/
munjeni said:
You can try! You no need to install, simple boot them without installing! On next reboot your phone will boot normaly! So boot these image temporary by command:
fastboot boot boot.img
Click to expand...
Click to collapse
Yeah but I just relocked my bootloader yesterday. I won't be unlocking it till I get more time in development.
crytic said:
Nope, doesn't seem to boot :/
Click to expand...
Click to collapse
Weird then... The patch I applied to port z1 kernel to z1 compact made a fully working stock kernel. But when I applied it to CM kernel it doesn't even boot. Can you by chance get a copy of /proc/last_kmesg and upload it somewhere or here?
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6nuname -r
uname -r
3.4.0cyanogenmod-g77098c0-dirty
~ # ←[6n
Click to expand...
Click to collapse
munjeni said:
Click to expand...
Click to collapse
Woot! There it goes Now I don't have to port CM haha!
Sweet, with or without display?
crytic said:
Sweet, with or without display?
Click to expand...
Click to collapse
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
munjeni said:
Click to expand...
Click to collapse
munjeni said:
With! Investigating between commits on git since using old working commits, need to find which commit broke display init. There is ~100 commits between but I will try every 20.th When commits get located than will try to fix upstream kernel . There is a lot of work but thats a only way by now.
Click to expand...
Click to collapse
git bisect to the rescue Well, if you need any help, just drop me a line!
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
That is all we need ! A custom kernel thant can handle GSI !
Voodoojonny said:
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
Click to expand...
Click to collapse
I've updated the link, you should see the uncompressed file in folder !
Or direct link : https://drive.google.com/file/d/1TvihsIa_XbtC66yaWRZ1EPY5UR6LLD5g/view?usp=drivesdk
Thanks
WiwiPouPou said:
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Click to expand...
Click to collapse
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
I've tried, maybe my image is bad, strange (I originally tried my stock source too, Google 4.9 toolchain, no luck). Can you test with the one in the link please ?
I will have access to my PC only next week...
Thanks a lot for your feedback !
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
WiwiPouPou said:
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
Click to expand...
Click to collapse
I used the original source code with some small changes (which are now included in official source) to make it compile.
Don't mind about the toolchain for the moment, gcc4.9 is most stable.
I don't have time trying this out atm, busy compiling los 15.1 but if you share exactly how you did it, (terminal log in pastebin and most importantly the exact errors, "doesn't work" doesn't help ) me or someone else might be able to help you (and you don't have to ask next time you get the error.
If you want you can start adjusting the lineage kernel, so i could build with los kernel which could save time towards working custom roms.
I successfully repack. But phone don't boot. (9.11 ROM)
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
artyom5613 said:
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
Click to expand...
Click to collapse
On which roms did you test your kernel?
Voodoojonny said:
On which roms did you test your kernel?
Click to expand...
Click to collapse
8.1 stock. 9.11
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
artyom5613 said:
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
Click to expand...
Click to collapse
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Thanks! O try to add kcal with this commits.
Yea, source for pie is not pushed. Xiaomi cant fix 8.1 kernel... Stock compiled kernel issue: wifi don't work...
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Can you tell me what version of kernel you use whyle compile kernel? I tryed on new 9.11, but phone dont boot.
Maybe when you compile version be 9.10 or ealier.
becouse ramdisk and kernel image can conflict
I hope this can support settings for "display temperature" so that we dont need app for calibrating warmth or coolness of display
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
artyom5613 said:
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
Click to expand...
Click to collapse
Kcal is working ?
Strange for WiFi, module not compiled ?