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??
Related
Please Don't Quote This Post,
It's Just way too big and would make any comment look stupid,
Thanks
Just When You Thought Your Favourite Dev Is Out Of Ideas... He Comes Up With This
ok so alot are complaining how we can't flash kernel away from the pc among other things (which ill get to later ), (mostly @One-X-master)
so i looked for a way to get around this and found Kexec as the answer.
Wiki said:
In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot,and can help systems to meet high-availability requirements by minimizing downtime.
Click to expand...
Click to collapse
however, with that comes managing online hardware which is somewhat problematic,
thus that prompted few people to come up with an ingenious solution called Kexec-hardboot.
Kexec-hardboot:This works by loading the kernel into memory and force restarting the phone with new kernel.
All of that with some ramdisk tweak allowed me to set a kernel at boot and restart to it,
avoiding having to flash it in the 1st place
Updating the kernel is called flashing..
A Flash is also what precedes Thunder
its also refered to as Lightning, Thus I came up with the name Kernel Lighter
Lighter= To Set Things On Fire/To Ignite (The Kernel)
Thus this is a kernel igniter
I Know, i've got to much time on my hand.
If you have a smart name, please do suggest.
Special Thanks: @Tasssadar: For His N7 Port, which made this port a breeze and for his help in debugging.
@Alex-V: Currently using his kernel as Base Kexec Kernel.
@Androguide.fr: For his recovery-less flash method.
@amarullz: For His AromaFM Source Code.
@LlabTooFeR: For His Stock Kernel.
@faux123: For His Kernel Source.
@mkasick: For The Original Port.
Sources:Alex-V 1.7 Kernel
Hardboot Patch
Faux Kitkat Kernel
AromaFM KL
Download Link In Post Below
Always have a backup.
Attachement & How-TO
ALL THE STEPS MUST BE FOLLOWED.
Requirements
S-off/Unlocked Bootloader
Android App & Recovery App
Fastboot flash boot Zeus.img
For ZeusKL.v10.img (New Layout) You must first switch to the new layout
Flashing Kernels Though Recovery
Boot Into Recovery
Flash AromaFM-KL.zip
Select Kernel Zip To Flash
Choose Flash Location
Choose Boot.img
Yes/No To Flash Zip (useful for flashing modules)
Reboot
Flashing Kernels Though Android(deprecated)
Start KL Android App
Choose Kernel Zip*
Kernel & Ramdisk
Reboot To Recovery --> Flash Modules
Reboot
* For zips to be listed, they must be placed in /sdcard/modules/
* otherwise click browse and happy hunting
Something Went Wrong:
Let say the phone wouldnt boot during kernel update after using the app,
the best solution would be to go back to stock kernel, look at the recovery flashable zips in Extras section,
If none seem to fit, try another custom kernel
if you still had no luck booting, you should try flashing that kernel through fastboot and see if it makes any difference.
Warning!!
Note: All the zips provided are flashable through both The App & Recovery... but I recommend recovery
BUT DON'T FLASH THE KEXEC (KL.Zeus.img) KERNEL THROUGH THE APP or Recovery,
as it will continuously boot itself over and over and over again.
Download Link In Post Below
Downloads
Kexec Kernel: KL.Zeus.img(CM12 Based)(V10)(Old Layout Only)
Kexec Kernel: KL.Zeus.img(CM12 Based)(v11)(New Layout Only)
Android App: KernelLighter.apk(No longer in active development, use the Recovery App instead)
Recovery App: AromaFM-KL Flasher(v4.1)(ZeusKL v9- only)
Recovery App: AromaFM-KL Flasher(4.6)(ZeusKL v10+ only)
Extras(deprecated)
Sense 5 Stock Kernel(Works on Sense 4+)(courtesy of LlabTooFeR) flash via recovery
ASOP/CM10.1(Android 4.1.2/4.2.2) flash via recovery
ASOP/CM10.2(Android 4.3) flash via recovery
Archieve
Multirom
ZeusKL
Thunder07 said:
& Another One.
Click to expand...
Click to collapse
Can't wait to try, sound incredible
Awesome! Looking forward to try it.
Sent from my Nexus 7 using Tapatalk 4
Someone tried it?
Never again without Sense 5! *~* <3
This i call development, thanks for that solution.
TouchscreenLover1 said:
Someone tried it?
Never again without Sense 5! *~* <3
Click to expand...
Click to collapse
i made a small typo in one of the files..
after flashing zip
do this
adb shell
mount /data -o rw
echo /data/boot/Kernels/Stock/boot.img-zImage>/data/boot/kernel
echo /data/boot/Kernels/Stock/boot.img-ramdisk.gz>/data/boot/ramdisk
Will Fix Zip soon
Edit: FIXED
Dexxmor said:
This i call development, thanks for that solution.
Click to expand...
Click to collapse
Anyone a Sense 5 Kernel.zip? Kexec boots a descriptet, will try this solution.
Dexxmor said:
Anyone a Sense 5 Kernel.zip? Kexec boots a descriptet, will try this solution.
Click to expand...
Click to collapse
this works on both sense 5 and 4+
i had this running for almost a week now on sense 4+
and just moved to sense 5 and thought it will be a good time to release this.
The Stock kernel comes from sense 5 ROM
I know, but back to 4.1.1 is not a solution for me (Sense 5 is the dealbreaker with AOSP ROMs )
Another Question, if i change to AOSP, it will work too? or must we flash (an not realeased) Kexec AOSP kernel? (i ask not for me, i ask for everyone on AOSP with ORD xD )
Dexxmor said:
I know, but back to 4.1.1 is not a solution for me (Sense 5 is the dealbreaker with AOSP ROMs )
Another Question, if i change to AOSP, it will work too? or must we flash (an not realeased) Kexec AOSP kernel? (i ask not for me, i ask for everyone on AOSP with ORD xD )
Click to expand...
Click to collapse
you dont have to go back to 4.1.1, this will work with sense 5 rom
if you want to use AOSP you must follow the custom kernel guide.
Ahh, (my english is bad..) i think we misunderstand each other, i asked for an Sense 5 kernel.zip to try your "Flash kernel in Recovery" Solution, it exists not so many Kernel.zip with the "Flash Kernel Script" to flash the kernel in recovery... I hope its clear what i mean
this wiil be work on maximus 21 ?
Yes
Dexxmor said:
Ahh, (my english is bad..) i think we misunderstand each other, i asked for an Sense 5 kernel.zip to try your "Flash kernel in Recovery" Solution, it exists not so many Kernel.zip with the "Flash Kernel Script" to flash the kernel in recovery... I hope its clear what i mean
Click to expand...
Click to collapse
im not 100% sure, but if you're looking for the zip, its in the 2nd post
the 1st time you must flash the kernel through fastboot AND zip through recovery,
later i will make an app that will work to replace kernels.
but even that all will require 1 flash through fastboot.
NOTE:
the zip contains to kernel, one that you flash in fastboot
one that will be copied to /data/boot/
the 1st is kexec which will boot the one in /data/boot/
Not clear enough xD, this (the kernel.zip) was not a request to you, it was an request to somebody to make me a flashable kernel zip, as an example repacked Alex-V kernel for Sense 5, to test this.
Its late here, so my explanation will suffer, sorry for that.
Dexxmor said:
Not clear enough xD, this (the kernel.zip) was not a request to you, it was an request to somebody to make me a flashable kernel zip, as an example repacked Alex-V kernel for Sense 5, to test this.
Its late here, so my explanation will suffer, sorry for that.
Click to expand...
Click to collapse
ok that was clear enough,
so far as far as i hear,
only trips kernel work with sense 5
Thanks, sorry for my poor english.
---------- Post added at 11:31 PM ---------- Previous post was at 11:18 PM ----------
EDIT: Now we can flash kernel without a PC, testet and it worked.
So, we can flash kernels through the rom itself by replacing boot.img in data/boot and reboot, can't we ?
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 ...
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
Hi all,
This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/showthread.php?t=2577211
With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827).
I adapted this method to be able to apply it quite easily on any android device.
This method includes few pieces of software ( sources will be published) :
kexec-hardboot : kernel patch from mkasic
hardboot-reserve : new kernel patch
kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.
Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.
Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )
Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.
You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ
Main advantages of using qcow2 :
thin provisionning
snapshots
compression
liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/showthread.php?t=2226889
Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
- standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
- livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
- liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
- fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
- livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
take dkp kernels for tw43 and kk4.4.2 : http://forum.xda-developers.com/showthread.php?t=2226889
or kernels I compiled
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.
Downloads : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
reserved
First
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.
Sent from my SCH-I535 using Tapatalk
Totally forgot about this, I'll have NBD included in my next kernel so this can work
this is awesome ! i been looking for muilt-boot since i got an S3 !
it's working great!
Awesome!
Now does it matter what bootloader you're on for this?
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.
Do these videos have audio? kinda hard to follow... or it just my laptop?
Restore
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
PwnCakes193 said:
Totally forgot about this, I'll have NBD included in my next kernel so this can work
Click to expand...
Click to collapse
I will add a link to your kernel in first message when it becomes compatible with qcow2 support.
vbetts said:
Now does it matter what bootloader you're on for this?
Click to expand...
Click to collapse
There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )
stanguay said:
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
Click to expand...
Click to collapse
As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?
Philippe,
ubuntu touch trusty in progress
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I remember the last time someone built Ubuntu Touch to the d2att S3, but we ran into the same issues as you previously mentioned. Will there ever be a way to get the data to work?
codemonkey98 said:
Will there ever be a way to get the data to work?
Click to expand...
Click to collapse
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Phil_Suz said:
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Click to expand...
Click to collapse
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
shekinahsmoke said:
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
Click to expand...
Click to collapse
Hi shekinahsmoke, no it is not necessary at all. It's better to install all zip in one shot, but I did this demo to show that you can come back to multiboot, select an already created rom and apply another zip ( gapps in this example ) even after first installation.
codemonkey98 said:
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
Click to expand...
Click to collapse
rani9990 said:
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Phil_Suz said:
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Click to expand...
Click to collapse
I'm glad to hear. I appreciate you shedding some light towards us with Ubuntu Touch and your support for multiboot. :good:
Hi All,
Multiboot v2.1 is now ready on same download link ( http://www.androidfilehost.com/?w=files&flid=12801 )
This version add support for unbutu touch 14.04.
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I would love to try your touch port I have been using your recoveries for a few weeks now and just flash the touch wip Rom that is on the site but to have a simi-working port to play with would be awesome.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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).
After some hard work i would like to present you my stock minimal kernel.
The goal of this kernel is to keep it minimal.
If someone like to help me, please contact me
Main features:
- minimal optimized kernel
Tweaks:
- kernel is free from dm-verity and root check
- disable a lot of debugging
Future:
- more minimal
- disable more debug
- some features
Installation:
You need an open Bootloader!!
This kernel is ONLY FOR H930!
You can flash the kernel inside twrp.
After flashing the kernel please install the neweset magisk root.
https://forum.xda-developers.com/app...mless-t3473445
Then wipe Dalvik/ART and Cache.
Feedback:
If you find some bugs or something is not working correct, please contact me.
Download:
https://drive.google.com/open?id=1f8YVCPvAq3N47AXbzAMY4OamHXealM_p
Credits:
Big thanks for jcadduono on his work with twrp and the kernel !!
XDAevDB Information
[KERNEL] [Stock] [H930] Minimal Stock Kernel
Contributors
djsven
Source Code: http://opensource.lge.com
OEM Kernel: Linux 3.x
Version Information
Status: Beta
Current Stable Version:
Created 2018-01-28
Last Updated 2018-01-28
Waiting anxiously
kherio said:
Waiting anxiously
Click to expand...
Click to collapse
Patiently taps fingers
Sorry for this delay.
But i have to fix a small problem with cgroups error logs.
If your kernel is as good as your modified rom... It's really worth it!!!
Hi to all..
Realy thanks.
Try to get a good working kernel is not realy easy.
The most problem is my time.
I compile a working kernel, but not have the time to fix all the issues.
So i need you help.
You is interesst to help me to test the kernel and provide me the log files?
Hi to all..
The Kernel is ready.
Who likes to test it?
Hi to all..
The Kernel is ready.
Who likes to test it?
I would love to
I am far away from my computer.... In case of bootloop... Will try it when I am back home??
Can you let me do some testing. I got plenty for time today.
Hi...so now its kernel time
Sorry for my second delay.
This is my test kernel for all who likes to test it.
You have to go to recovery and flash it
PLEASE BACKUP YOUR BOOT Partition!!
So you can flash back yout stock kernel
If you flash back boot partition , you have to rename inside /system/lib/modules the texfat.old to texfat.ko. This is the stock texfat module which we cant use for custom kernel for now.
https://drive.google.com/open?id=1EBN7TqZYdD94cPEoFv30iUOkNO9K800b
great.. another step forward to custom kernel
i flashed it right now and will repoprt if i see anything
thanks for your work
Thanks.
This was a realy hard work and took a long time
Small features too this V1 Kernel:
- Kernel is undervolted
- Remove a lot from debug
- Remove a lot nonsene logging
- Optimize some settings / parameters
flashed and testing So far no bugs. Great work!
Thanks for Info.
Have you exfat sdcard inside?
V2 Beta is online...
Correct some changes..
I've just installed your V2 with no problems at all... I had to reboot twice for magisk to pass safety net.. Everything seems to be working OK... What differences should I be noticing?
Thanks for your hard work on this kernel.
. I have been rooting phones for about 12 years now and I am always always impressed with the time and skill you guys put in...
Thanks again
djsven said:
Thanks for Info.
Have you exfat sdcard inside?
Click to expand...
Click to collapse
Sorry for the late response Yup, i got.
Flashed v2, still no bugs, running like a charm
Thanks for info..
Next Kernel is coming ..testing it now..
- UV
- GPU lower step
- more debug removed