Related
Hello everyone,
Stock+ Team ($omator & Grooby) are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROM by Samsung.
Why should i use this kernel?
Our kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel it's like stock just rooted, and there is small chance (or any chance) that it will be detected as modified by service center at the first look
Please find latest of kernels listed below:
*NEW* ROOTED! I9000XXJW4 - Gingerbread (2.3.6) - CL: 1043937 - B.Date: 19-03-2012 - Download HERE!
Instructions:
1. Flash zImage.tar of choosen kernel using Odin (you will find it in package)
2. Profit!
What's included in this kernel
- Base image of kernel is 100% pure stock by samsung
- ClockworkMod Recovery added !
- Fully rooted (after flash you will have superuser and su installed)
Nothing more, nothing less - Enjoy!
If you like our modifications, support us with even a little donation for a beer -> Click to donate!
Don't forget to follow our service at Twitter (@SamsungUpdates) or (soon) Samsung-Updates.com
Best regards for CF for showing us the way and all XDA-DEVELOPERS members! we love ya!
This will be interesting. *[Subscribing]*
Thanks, I also prefer to use an stock kernel with the only addition of root features.
Lot of 2.3.5 custom kernels are based on 2.3.4 sources and also have tweaks that might do more bad than good.
Imho if those tweaks were so good samsung would have added them to their roms, it wouldn't be the first time they do that.
Enviado desde mi GT-I9000 usando Tapatalk
where it's ? no file posted
when its done, soonish =) tool is almost finished
ITs finished, download, test and let us know
Grooby said:
Hello everyone,
Stock+ Team ($omator & Grooby) are proud to bring you the latest insecure kernels based on stock kernels that you may find in ROM by Samsung.
Insecure kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel looks/feels like stock.
Please find latest of kernels listed below:
JVU: Download HERE!
Instructions:
Code:
1. Flash zImage.tar of choosen kernel using odin (you will find it in package)
2. enable usb debugging in settings->applications
3. while still connected and odin/kies is turned off, run RUNME.BAT (also in package)
4. Install latest Superuser.apk from market!
5. Profit!
best regards to ChainFire for showing us the way!
and of course for all XDA-DEVELOPERS members! we love ya!
Click to expand...
Click to collapse
XWJVU?
10chars
Added next (looks like latest) kernel, and more details to them
hack the planet =)
ROOTED! I9000XFJVA - Gingerbread (2.3.5) - CL: 621561 - B.Date: Tue Oct 4 KST 2011 added for
[ROM] XFJVA - JVA_JV1_JVT.tar [04.10.2011] [ANDROID 2.3.5] [MULTICSC] [KIES]
Original ZIP from Kies GT-I9000 TSR (Serbia & Montenegro) TEST MODE
is it possible somehow to add CWM to these kernels?
These are suppoused to look/feel/work as oryginal kernels just with rooted by default. We are currently working on extending default recovery menu with some features invisible for a service eye but useful for flashing custom roms
Thank you man!
It's possible to add JVT?
JVT Added, enjoy!
added to first post ROOTED! I9000XXJVT - Gingerbread (2.3.5) - CL: 617736 - B.Date: Thu Sep 29 KST 2011
for [FIRMWARE] XXJVT Android 2.3.5 Build Date Sep 29 DOWNLOAD
thank you! great work!!!
is it possible to unroot???
yes by flashing stock kernel zImage - we will update first post with those later
hey
i flashed it and installed superuser.apk
rooting worked fine
however, when i downloaded rom manager from market for cwm... i try to flash in recovery but says theres an error
" E: failed to verify whole - file signature
E: signature verification failed
installation aborted
any ideas please ?
because there is no custom clockworkmod recovery installed
try installing rom manager and flashing recovery from there
youre looking for Flash ClockworkMod Recovery and pick i9000
MTD is for cyanogen so pick normal version
should work
actually thats wut ive done... and it gave me an error
but let me be sure
i run the runme.bat file from the extracted file on desktop while usb is still connected and kies not ?
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??
Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame
Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game
Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app
Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game
hi guys
i want to compile rom for ancora but i dont know anything about this job
im begiiner and i want to help from you
my only request is editing commits(simply changing,wiritng and deleting) in roms(github repos)
example i want to change some commits on arco's kernel and rom (samsung msm7x30 and android device ancora) and then make a flashable zip for rom
i dont have account of github i know i must get account
and then what must i do?
probably for compiling ron i must install ubuntu into my pc
i dont want to rebuild rom or build new rom i just want editing commits in some roms
can someone make instruction list for me?
Hello everyone! Thanks to @educk and @h0rn3t for their awesome dualboot project for ancora, and @theloneseeker for his amazing tutorials, I've managed to make ION kernels compatible for dualboot in secondary ROMs, in other words, you're primary ROM can be ION or non-ION, but the secondary ROM had to be non-ION build to work, but now, I've managed to make ION builds dualboot compatible. Therefore, CyanogenMod 10.1 beta 3, CyanogenMod 10.2 alpha 5, CyanogenMod 11 20140323 build (the final 20140413 seems to be unstable for some) and Dark CyanogenMod beta 3 can be installed as secondary ROMs. The procedure on how to dualboot is mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2469803, but I will still provide you with a similar guide in order to avoid errors.
**Installation Guide**:
1- Download the Dualboot1.8.apk from the mentioned thread above in the downloads section.
2- Install busybox and the Dualboot1.8.apk and grant the app root access.
3- Tap on Partitions and set the partition table according to your preference (I have a 4Gb external SD card so there are no exact values for everyone). This step takes most time so be patient.
4- Once done, tap on Tools and then Prepare flashable zip, and direct it to the ROM.zip you want to have as your secondary ROM (ION builds are now working)
5- Choose to wipe data and cache, then choose to Flash now. In recovery, tap on flash untrusted zip and after flashing is done, reboot.
6- Using a file explorer, you will see on your internal SD card that a Dualboot folder exists, and according to your secondary ROM, create a 4.2.2 (for CM 10.1) or 4.4.2 (for CM 11) and place the corresponding boot2.img that I provided. So, you should have something like Dualboot/4.4.2/boot2.img for example.
7- Go back to the Dualboot app and tap on Switch
Viola! Now, you will have ION build secondary ROM! You can have two 4.4.2 ROMs as well, or any other combination
NOTE: The kernels I made are 100% tested by me and are working with no issues whatsoever.
Credits:
-CyanogenMod Team
-Mr. Arne (arco68) for all his work.
-Mr. Radu (arsradu) for his kernel collection and bringing CM 10.2 for our device.
-Osama (Madridii) for his kernels and all his wonderful work and D CM 11 :highfive:
-Daniel (theloneseeker) for his amazing tutorials
-educk and h0rn3t for bringing dualboot feature to the i8150! :victory:
-Roderick (Tazerick) for motivating me
-lafactorial for his powerful Khan Kernel!!
-hurtsky for the rock solid HurtSky kernel!
-sir mordred for bringing TRIM to the ol' i8150 (perfectly working with dualboot)
P.S. If any user wants to have his custom kernel work with dualboot, please give the name of the kernel, the kernel version, the linux version and a link to download the kernel, and post what ROM the kernel works with (e.g. xxx kernel version x.xx.xx working with CyanogenMod X.X) and I will do my best in making the kernel work with dualboot.
I AM responsible for any damage that may happen to your device. I do not own any of the kernels or ROMs or apps that have been used to make this project possible. If any user encounters an issue, kindly report the issue and post exactly what your steps are. The guide posted here is the same as educk mentioned but maybe more simplified. I do not deserve any credit, I only made the kernels dualboot compatible but I didn't build these kernels. The kernels posted are the default kernels of the ROMs (simply extracted the boot.img only). Good luck to everyone
Download links:
- https://drive.google.com/file/d/0BxQMaqAowdtsYkl4WnItQ3dfbDA/edit?usp=sharing
- https://drive.google.com/file/d/0BxQMaqAowdtsRDFmTjRBaGdJU1U/edit?usp=sharing
- https://drive.google.com/file/d/0BxQMaqAowdtsRW1HNlQzQjJ1QkU/edit?usp=sharing
- https://drive.google.com/file/d/0BxQMaqAowdtsWk5EVVF5VlM1ZUU/edit?usp=sharing
If any link doesn't work, I will add mirrors
XDA:DevDB Information
Ancora DualBoot, Kernel for the Samsung Galaxy W I8150
Contributors
Paul_Kolanjian, arco68, educk, h0rn3t, arsradu, Madridii, theloneseeker, lafactorial, hurtsky
Kernel Special Features: Dualboot + All awesome kernel features made by the respective developers
Version Information
Status: Testing
Created 2014-04-23
Last Updated 2014-08-21
More kernels support
Added CyanogenMod 10.2 and 11 ION kernels linux 3.4.86 dualboot from Mr. Radu's kernel collection
Added KhaN Kernel 3.4.87 [362 MB] dualboot. Big thanks to the one and only lafactorial!!
Added HurtSky Kernel v1.3. A warm thank you for the senior member hurtsky for his kernel
Added CyanogenMod 10.1 Beta 4 Linux kernel 3.4.89.
Added CyanogenMod 10.2 Linux kernel 3.4.89.
Added CyanogenMod 11 Linux kernel 3.4.91 which is for latest CyanogenMod 11 built by Mr. Arne on 21st of May.
Added HurtSky kernel v1.5 Linux kernel 3.4.90 and HurtSKy kernel v1.5.1 Linux kernel 3.4.91.
Added CyanogenMod 11 kernel based on 25th of May build by Mr. Arne.
Added KhaN Kernel Linux 3.4.91 [360 MB] with TRIM support. Thank you sir mordred for all your wonderful effort and lafactorial for updating your kernel with a blazing update!
Added CyanogenMod 11 Linux kernel 3.4.100 from the 1st of August build of Mr. Arne
Added Hurtsky Kernel v2.6 Linux 3.4.101
Added K^Kernel v1.5 Linux Kernel 3.4.101 416 MB thanks to the best of the best XDA Recognized Developer Christopher83
Download links:
- CM 10.2 Linux 3.4.86 https://drive.google.com/file/d/0BxQMaqAowdtsWmRnc1NrVzEwRlU/edit?usp=sharing
- CM 11 Linux 3.4.86 https://drive.google.com/file/d/0BxQMaqAowdtsY0l0TG1TX3UyQk0/edit?usp=sharing
- CM 11 KhaN Kernel Linux 3.4.87 https://drive.google.com/file/d/0BxQMaqAowdtsYkszS2xuTnR4Rzg/edit?usp=sharing
- HurtSky Kernel Linux 3.4.83 https://drive.google.com/file/d/0BxQMaqAowdtsYXExamtWbEdXRVE/edit?usp=sharing
- CM 10.1 Beta 4 https://drive.google.com/file/d/0BxQMaqAowdtsUDl5RktlODdOcU0/edit?usp=sharing
- CM 10.2 Alpha 7 https://drive.google.com/file/d/0BxQMaqAowdtsNkxqR0dQTWd2MGM/edit?usp=sharing
- CM 11 21st of May https://drive.google.com/file/d/0BxQMaqAowdtsY0x2UXF2cUhkY28/edit?usp=sharing
- Hurtsky kernel v1.5.1 https://drive.google.com/file/d/0BxQMaqAowdtscUIxRkdxX2FPQ3M/edit?usp=sharing
- Hurtsky kernel v1.5 https://drive.google.com/file/d/0BxQMaqAowdtsUXA1dVJ4d2Jfc3M/edit?usp=sharing
- CM 11 25th of May https://drive.google.com/file/d/0BxQMaqAowdtsRC1mNVNTaDI0QkU/edit?usp=sharing
- CM 11 TRIM Kernel (based on KhaN Kernel) https://drive.google.com/file/d/0BxQMaqAowdtsVWtvTUpySTV4bDQ/edit?usp=sharing
- CM 11 1st of August https://drive.google.com/file/d/0BxQMaqAowdtsZ09XMEtxYmZYV28/edit?usp=sharing
- Hurtsky kernel v2.6 https://drive.google.com/file/d/0BxQMaqAowdtsdmxJcFRNZXdKQVE/edit?usp=sharing
- K^Kernel v1.5 416 MB https://drive.google.com/file/d/0BxQMaqAowdtsWW42ZVpKaUtOM0U/edit?usp=sharing
***UPDATE***: Thanks to @theloneseeker for pointing it out, the new kernels are compiled with the extra lib files included inside. Install them using the same procedure above, happy dualbooting!!
yaay I'm in credits Great job man!
Paul_Kolanjian said:
Added CyanogenMod 10.2 and 11 ION kernels linux 3.4.86 dualboot from Mr. Radu's kernel collection
Added KhaN Kernel 3.4.87 [362 MB] dualboot. Big thanks to the one and only lafactorial!!
Download links:
- https://drive.google.com/file/d/0BxQMaqAowdtsOEJoeVgzMmQ1c1U/edit?usp=sharing
- https://drive.google.com/file/d/0BxQMaqAowdtsTUxhYWZPU1pUM2c/edit?usp=sharing
- https://drive.google.com/file/d/0BxQMaqAowdtsVERPVkxjNFVXaVk/edit?usp=sharing
The new kernels require lib files in addition to the boot2.img, so I included the files with them. All you have to do is put all the files together in the sub-folder of your kernel for example Dualboot/4.3.1/**put boot2.img and all other .ko files here**
Click to expand...
Click to collapse
Awesome thread and great work buddy..
nice work
thanks for this awesome work you saved me a lot of work, time & trouble
by the way I'm creating a dualboot super thread with all info about dual booting
a tutorial created by me and links to all threads about it
the ion problem was a major bummer but now we are good to go
Thanks man! :good: a question: can i use a ICS ROM as primary ROM, like it was with the dualboot by educk?
Edit: and the dualboot can affect performances/battery life?
Inviato dal mio GT-I8150 utilizzando Tapatalk
Very Important Note for 4.4.2 dualbooters
micnicmic said:
Thanks man! :good: a question: can i use a ICS ROM as primary ROM, like it was with the dualboot by educk?
Edit: and the dualboot can affect performances/battery life?
Inviato dal mio GT-I8150 utilizzando Tapatalk
Click to expand...
Click to collapse
Sure you can my friend, the primary ROM can be any Android ROM even Gingerbread, but the secondary ROM must be Jellybean and upward (tried making Gingerbread kernel dualboot compatible but it soft-bricked my phone). I repeat, this is the same procedure as educk and h0rn3t posted and all I did is add kernels to make ION kernels compatible to feed my dualboot hunger and the others as well
As for the performance and battery life, dualboot has nothing to do with it, instead, the ROM and kernel you use (on the primary and secondary partitions) are what determines the performance, e.g. if you use CM9 with hurtsky kernel on primary ROM and CM11 with stock kernel on secondary ROM, it's the same as saying you are 100% using CM9 on primary and similarly for CM11 and dualboot has no effect whatsoever on your combination, in other simplified words, dualboot for ancora by educk and h0rn3t is amazing (better than the one I have on i9100) since it creates two phones in one, so performance is based on what you are using.
***IMPORTANT NOTE*** After some testing, I realized that two custom kernels on primary and secondary Kitkat ROMs breaks the secondary ROM's WiFi and GPS, so if you are using CM11 with Khan Kernel on primary, and any other 4.4.2 ROM with hurtsky or khan kernel as well on secondary ROM for example, you will not be able to use WiFi and GPS whereas primary ROM remains unaffected, and the battery life and performance on secondary ROM are unaffected and the same as using it as primary ROM. The same happens if you use the same custom kernel on primary and secondary ROMs. So if anyone dualboots two 4.4.2 ROMs like me, use custom kernel on primary ROM and stock ROM kernel of the ROM you're using (download links are in first post). This has been tested on Android Kitkat so I don't know the consequences of two custom kernels on Jellybean. Just wanted to add this as a "Heads-up" so no one spams the threads of CM11 or any other thread accidentally. Good luck to all fellow dualbooters!!!
Will you make new cm11 kernel ready for dual boot?
Inviato dal mio GT-I8150 utilizzando Tapatalk
micnicmic said:
Will you make new cm11 kernel ready for dual boot?
Inviato dal mio GT-I8150 utilizzando Tapatalk
Click to expand...
Click to collapse
Of course I will my dear brother , all you have to do is ask and I'll supply you with a big number of kernels! I honestly stopped updating the thread since I believe that adding kernels just it would not interest users, but it's about time I release updated kernels. Feel free to post any kernel you want for any ROM, and I'll add it for you and everyone once it's done. By the time you read this post, I'll be adding new kernels in the second post, and I come with excellent news about the KitKat dualboot issue mentioned up there in the sixth post.
In order to fix the issue that persists upon dualbooting two KitKat 4.4.2 ROMs (in which using a custom kernel instead of the original ROM's kernel on the secondary ROM is breaking the secondary ROM's WiFi and GPS), the solution is quite simple. As I previously said, the primary ROM, no matter what kernel you use, is not affected. So, here it goes. Let's assume you want to install the latest CyanogenMod 11 build by Mr. Arne which was built on the 21st of May, and you decided to install the ROM on the secondary partition, but you want to install the latest HurtSky kernel with the build, yet, you know that custom kernels are breaking some essential components on the secondary ROM (In fact, this happens with any ROM other than KitKat if you use a custom kernel, and the fix works for any Android version). All you have to do is download the latest HurtSky kernel .zip file, extract the "system" file included with the kernel (there is META-INF folder, system folder, and boot.img, but we only need the system folder). Open the CyanogenMod-11.zip you want to install using WinRAR or WinZip or 7zip (basically any archiver should work), you will also see the same folders, but you need to navigate to /system/lib/modules and you will see some .so files (about 6), so delete them all. Replace these files with the .so files we extracted from the HurtSky kernel we downloaded (remember the extracted "system" folder from HurtSky's kernel) and once all the files are in place, your CM 11 ROM is ready for dualboot BUT ONLY to be used with the HurtSky custom kernel. IF you want to use another kernel, or maybe the default one, do the same steps as above and WiFi won't be affected anymore. Here is a listed summary:
1- Download the ROM.zip you want, open it and navigate to system/lib/modules.
2- Delete all the .so files found in the /system/lib/modules folder (only the files that look the same in the kernel's /system's folder)
3- Download any custom kernel you like to use in the secondary ROM, open it, and extract the "system" folder.
4- Add the .so files in the extracted 'system" folder from the kernel to your ROM.zip in /system/lib/modules.
5- You now have a dualboot-ready ROM to be used with the specific custom kernel you chose. (always make a NAndorid Backup just in case)
If anyone faces any issue or wants to have a new kernel, I am more than happy to help, give solutions, and add up some more kernels. As I said, I will be always testing dualboot to find any issues and reproduce them in order to be fixed. I always dualboot two 4.4.2 ROMs (currently on Paranoid Android by my brother Osama, and the latest CyanogenMod 11 build by Mr. Arne). Have any request? Need some help? Don't be shy to ask! Good luck to everyone!
:good: really thanks for all your work, I really appreciate this dual boot feature
Inviato dal mio GT-I8150 utilizzando Tapatalk
Hey! Will you make the new kernels ready for dualbooting? Thanks in advance!