[KERNEL][STOCK][JB][8 MAY] Blazing Kernel v8 - Payback Time!

Status
Not open for further replies.
Search This thread

Infinite96

Senior Member
Aug 1, 2012
3,204
1,887
Hey guys...I will be flying to Australia on the 13 Feb to further my studies...so will take quite some time to settle down...until then, I don't know when I can get time to continue my dev stuff, but will do when I have time...so till then...:)
Okay ! Great that you're having your study and education in a great country :p
Enjoy your study there :p
 

Ryuinferno

Senior Member
Apr 3, 2012
3,548
7,112
ryuinferno.github.io
Re: [KERNEL][STOCK][ICS][27 Jan] Blazing Kernel v2

Whats the use of a custom ROM but no CWM? So here's a little teaser...:p

Screenshot_2013-02-11-13-47-35.png


Special thanks to iXanza for being the white mice...:D
 

TarunBHart

Senior Member
Jun 7, 2012
136
7
ludhiana
Re: [KERNEL][STOCK][ICS][27 Jan] Blazing Kernel v2

Us there any other features except th cwm.anyways congrats fir thia achievement will wait for your update

Sent from my GT-I9100G using xda premium
 

mesol

Senior Member
Apr 29, 2012
74
5
Cheras
Redmi K20 / Xiaomi Mi 9T
I flashed official JB 4.1.2. I flashed your kernel just for the sake of having CWM so that I can install custom ROM. My phone freezed, maybe due to incompatible kernel, then I'm using Volume Up + Home + Power ton enter Recovery. Flashed my custom ROM (CM10).

Is this ok to follow this steps? By using steps above, I basically flush out your kernel, replacing CM10 kernel however maintained CWM?
 
Last edited:

Infinite96

Senior Member
Aug 1, 2012
3,204
1,887
I flashed your kernel just for the sake of having CWM. My phone freezed, then I'm using Volume Up + Home + Power ton enter Recovery. Flashed my custom ROM (CM10).

Is this ok to follow this steps? By using steps above, I basically flush out your kernel, replacing CM10 kernel however maintained CWM?
I don't get you ...
Did you mean .. Flashing BlazingKernel on the XXLSR JellyBean Release ? O.O
 

Infinite96

Senior Member
Aug 1, 2012
3,204
1,887
Yes, sorry. I just realize that I giving insufficient info. Edited above post.
Hmm..No you can't =) You can't maintain CWM in StockROM currently by flashing ICS's kernel on it ;P
But you can use the CWM inside the kernel to flash stuff.
Anyhow Ryuinferno will give an update for the kernel soon .
Stock kernel with CWM . Don't worry =)
 

gp545

Senior Member
Jul 7, 2012
1,390
1,181
33
Bangalore
OnePlus 7 Pro
I flashed official JB 4.1.2. I flashed your kernel just for the sake of having CWM so that I can install custom ROM. My phone freezed, maybe due to incompatible kernel, then I'm using Volume Up + Home + Power ton enter Recovery. Flashed my custom ROM (CM10).

Is this ok to follow this steps? By using steps above, I basically flush out your kernel, replacing CM10 kernel however maintained CWM?

You're right. Your phone froze because V2 Kernel is made for 4.0.4/4.0.3 :)

If you've flashed CM10 means, you have CM Kernel by default which comes with CWM with it I guess :)
 

mesol

Senior Member
Apr 29, 2012
74
5
Cheras
Redmi K20 / Xiaomi Mi 9T
My above steps not workout. I managed to flashed custom ROM, ie JellyBam but stuck at bootloader.

I did try using temporary CWM by Jiangyi but giving 'verification error'. Btw, thanks for replying and sorry for thread owner for messing up your thread.
 

iXanza

Inactive Recognized Contributor
Apr 26, 2011
3,797
2,412
Redmi K20 Pro
Google Pixel 6 Pro
Re: [KERNEL][STOCK][ICS][27 Jan] Blazing Kernel v2

My above steps not workout. I managed to flashed custom ROM, ie JellyBam but stuck at bootloader.

I did try using temporary CWM by Jiangyi but giving 'verification error'. Btw, thanks for replying and sorry for thread owner for messing up your thread.

Basically you want to get to AOSP ROM like JellyBam right? If you're on 4.1.2 you can do this

Backup your files
Flash this kernel or lp7 kernel by codeworkx through temporary cwm
You won't be able to boot into 4.1.2 anymore. Remove the battery and boot into recovery by using vol up menu and power.
Perform a full wipe. Wipe data and format system. < important.
Flash jellybam.
Wipe data again < important.

Reboot. you should be set
 
  • Like
Reactions: mesol

mesol

Senior Member
Apr 29, 2012
74
5
Cheras
Redmi K20 / Xiaomi Mi 9T
Basically you want to get to AOSP ROM like JellyBam right? If you're on 4.1.2 you can do this

Backup your files
Flash this kernel or lp7 kernel by codeworkx through temporary cwm
You won't be able to boot into 4.1.2 anymore. Remove the battery and boot into recovery by using vol up menu and power.
Perform a full wipe. Wipe data and format system. < important.
Flash jellybam.
Wipe data again < important.

Reboot. you should be set

You are lifesaver, man. After struggling since last night. I managed to install JellyBam on top of official JB 4.1.2. YES, full wipe before and after flash jellybam is the KEY.

I do not perform full wipe before flash jellybam previously and it stuck on bootloader. Now its working!!
 

iXanza

Inactive Recognized Contributor
Apr 26, 2011
3,797
2,412
Redmi K20 Pro
Google Pixel 6 Pro
Re: [KERNEL][STOCK][ICS][27 Jan] Blazing Kernel v2

You are lifesaver, man. After struggling since last night. I managed to install JellyBam on top of official JB 4.1.2. YES, full wipe before and after flash jellybam is the KEY.

I do not perform full wipe before flash jellybam previously and it stuck on bootloader. Now its working!!

Glad it worked out. Enjoy your phone.

Sent from my GT-I9100G using xda premium
 

freakingprime

Senior Member
Jul 2, 2012
274
44
Hi.

I'm using rom xylon (based on aosp 4.2.1) with greenblob kernel. I tried to flash Blazing v3 kernel, but my phone atuck after showing i9100g text. The screen is noisy and jammed. Does blazing v3 support 4.2.1 aosp?
 

kanivier

Senior Member
Apr 6, 2011
401
78
nairobi
www.facebook.com
Re: [KERNEL][STOCK][JB][12 FEB] Blazing Kernel v3

Am tempted to flash but I ain't sure do the 1st method increase binary count too....

---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------

Hi.

I'm using rom xylon (based on aosp 4.2.1) with greenblob kernel. I tried to flash Blazing v3 kernel, but my phone atuck after showing i9100g text. The screen is noisy and jammed. Does blazing v3 support 4.2.1 aosp?
Did u read the 1st floor " any JB ROMs will only work if you did not modify the preload partition (wipe it or flash a new ROM via ODIN"
 
Last edited:

iXanza

Inactive Recognized Contributor
Apr 26, 2011
3,797
2,412
Redmi K20 Pro
Google Pixel 6 Pro
Re: [KERNEL][STOCK][JB][12 FEB] Blazing Kernel v3

Am tempted to flash but I ain't sure do the 1st method increase binary count too....

---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------


Did u read the 1st floor " any JB ROMs will only work if you did not modify the preload partition (wipe it or flash a new ROM via ODIN"

First method doesn't increase binary counter. And your second part of the post doesn't make sense.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 69
    **You can choose between TWRP or CWM now!!! :D**


    Blazing Kernel v8

    Yeah! As we all know, there are not many choices of kernels for our I9100G, especially stock kernels. Therefore, I decided to take up this challenge! After months of trials, hair-pulling moments and countless errors (and non-stop flashing too)...so now you have it: Blazing Kernel!

    Features for v3 and above (JB):
    - Can be flashed directly using stock recovery!
    - Compiled using Samsung _CHN_JB_Opensource_Update1
    - 2 versions of recovery available (different zImage): TWRP and CWM!
    - Init.d scripts support (Place scripts in /system/etc/init.d or /data/etc/init.d)
    - 3 versions of CWM recovery available (different zImage): CWM5, CWM6 and CWM5 Touch! (v4 onwards only supports CWM6)
    - Default scheduler is cfq
    - Default governor is interactive
    - MMC_CAP_ERASE already disabled by Samsung -> no more brick bug
    - Supports CIFS
    - Merged the touch screen fix in CM 10.1 by ankitkv
    - USB fast charge (use an app called "Fast Charge" to toggle)
    - Custom voltage settings (use "Voltage Control" to set)
    - Custom bootanimation (just place bootanimtion.zip in /system/media; to restore original bootanimation, just delete the bootanimtion.zip in /system/media)
    - Custom boot sound (just place PowerOn.ogg in /system/media; to mute, create an empty file named "mute" in /system/media; to unmute, create an empty file named "unmute" in /system/media ; to restore original boot sound, create an empty file named "ori_sound" in /system/media
    - Frandom support!
    - Patched /dev/random
    - Tweaked interactive governor to unleash its full power! :p
    - More RAM (original=769 MB, Blazing Kernel=771MB)
    - Additional governors: HYPER, Scary, wheatley, abyssplug, minmax, interactiveX, lulzactive, lazy, pegasusq, lagfree, smartassV2
    - Addtional I/O schedulers: vr, sio, row
    - Miscellaneous tweaks
    - More to come!​

    Features for v2 (ICS):
    - Can be flashed directly using stock recovery!
    - Compiled using Samsung Open Source Update 2
    - 3 versions of CWM recovery available (different zImage): CWM5, CWM6 and CWM5 Touch!
    - Default scheduler is noop
    - Default governor is interactive
    - Fixed 30 fps bug! (integrated the fix in BL ROM into the kernel)
    - Disabled MMC_CAP_ERASE -> no more brick bug
    - init.d scripts support (Just create a folder named "init.d" in /system/etc and insert your scripts in there)
    - Custom bootanimation support (Place bootanimtion.zip in /system/media, if none is present, default Samsung bootanimation will run instead)
    - Custom boot sound support (Place PowerOn.ogg in /system/media, make a file named "mute" to mute the boot sound, make a file named "ori_sound" in /system/media to restore original sound)
    - Merged the touch screen fix in CM 10.1 by ankitkv
    - Supports CIFS
    - Custom user defined voltages (use apps like Voltage Control)
    - RAM overclock! (From 400Mhz max to 533Mhz)(cannot be set, embedded in kernel)
    - Miscellaneous tweaks​

    Bugs:
    For v3 and above:
    - Currently none

    For v2:
    - Bluetooth is still not working in 4.0.4 ROMs (although the source code was updated)...hmm...yea...good job Sammy...:(

    Requirements:
    - Running a stock or stock-based Samsung TouchWiz ICS/JB ROM​

    Instructions:
    Flash via stock or custom recovery (Safest and easiest method):
    1. Choose your CWM version: CWM5, CWM6 or CWM5 Touch, v4 onwards only supports CWM6 and TWRP.
    2. Download the corresponding zip package.
    3. Place in sdcard (external sdcard for those running stock recovery)
    4. Flash the zip.
    5. Reboot.

    **Note: From v6 onwards, ODIN flashable kernel will not be released anymore as external modules are required...which is only achievable via zip files...

    Flash via ODIN (WARNING: Will increase binary count and warning triangle will appear):
    1. Choose your CWM version: CWM5, CWM6 or CWM5 Touch, v4 onwards only supports CWM6.
    2. Download the corresponding tar package.
    3. Run ODIN and select the tar package under PDA
    4. Start flashing.
    5. Reboot.​

    NOTE:
    To those who still thinks that it is my kernel that causes the SOD, you are more than welcome to revert to the stock kernel. Steps as below:
    1. Download stock_XXLSR_kernel.zip from here: http://bit.ly/XCEejd and place it into your external sdcard/internal sdcard.
    2. Flash it and you will be back to stock kernel and recovery.
    3. To flash stuff or do backups/restore, use this temporary CWM that was compiled by me: Temp_CWM6.zip. Since I compiled it using our device's kernel code, it should be more stable than the temporary touch recovery, and the labeling of partitions are correct too, plus it supports /preload...

    To those who wanna provide logs, kindly refer to this post: http://xdaforums.com/showpost.php?p=39014273&postcount=201

    Frandom
    v6 and onwards supports frandom, which is a faster (10-50 times) random number generator than urandom...it generally decreases lag in GUI...if you are using CrossBreeder, it will automatically utilise it...if not, place this script in /etc/init.d and set permissions as rwxrwxrwx (name it whatever you want) and reboot:

    Code:
    #!/system/bin/sh
    # Ryuinferno @ XDA
    
    chmod 666 /dev/frandom
    mv /dev/random /dev/random.ori
    mv /dev/urandom /dev/urandom.ori
    ln /dev/frandom /dev/random
    ln /dev/frandom /dev/urandom

    It is working if you have /dev/random.ori and /dev/urandom.ori after a reboot...to revert, just remove the script (or else, it will be applied on every boot)...​

    Downloads:
    For flashing via recovery:


    For flashing via ODIN:


    Thanks to them for their guidance: :D
    superatmos
    bluefa1con
    codeworkx
    Phil3759


    Enjoy guys! :D
    22
    Changelog:
    Code:
    [U]v1:[/U]
    - Initial release
    
    [U]v2:[/U]
    - RAM overclock to 553 Mhz
    - Disabled GENTLE_FAIR_SLEEPERS
    - Modified touchscreen sensitivity by codeworkx
    - Custom voltage support
    - Custom boot sound support
    - Optimised memcpy and memmove
    - Re-tuned interactive and hotplug governors (previous was either not performing or uses too much battery)
    
    [U]v3:[/U]
    - JB initial commit
    
    [U]v4:[/U]
    - Modified CWM in order to support preload (Thanks to [URL="http://xdaforums.com/member.php?u=4666971"]Phil3759[/URL])
    
    [U]v5:[/U]
    - Init.d scripts support (Place scripts in /system/etc/init.d or /data/etc/init.d)
    - Reverted certain interactive governor tweaks (too aggressive)
    - Replaced cpuidle files with old ones (from ICS source) for possible solution to SOD
    - Reverted configurations that might be the cause of unstability
    - Merged the touch screen fix in CM 10.1 by ankitkv
    
    [U]v6:[/U]
    - TWRP
    - USB fast charge 
    - Custom voltage settings 
    - Custom bootanimation
    - Custom boot sound
    - Frandom support
    
    [U]v7:[/U]
    - Samsung MEA_JB Open Source update (hopefully no more SODs)
    
    [U]v8:[/U]
    - Samsung CHN_JB_Opensource_Update1 (everything should be smoother & SODs are unlikely to occur)
    - Reduced size of zImage 
    - Optimised memcpy and memmove
    - Updated CWM to 6.0.3.1 and TWRP to 2.5
    - Patched /dev/random
    - Added governors: HYPER, Scary, wheatley, abyssplug, minmax, interactiveX, lulzactive, lazy, pegasusq, lagfree, smartassV2
    - Added schedulers: vr, sio, row
    - Compiled using O3 flag

    Source code:
    https://github.com/Ryuinferno/GT-I9100G-Blazing_Kernel
    17
    Ho yeah! So I managed to do it! I modified the CWM and now it will backup and restore the /preload partition...the basic functions of a kernel is complete now...future releases will be on features and improvements...:) Links and changelog in first post...

    *P.s. To those who still thinks that it is my kernel that causes the SOD, you are more than welcome to revert to the stock kernel. Steps as below:
    1. Download stock_XXLSR_kernel.zip from here: http://bit.ly/XCEejd and place it into your external sdcard/internal sdcard.
    2. Flash it and you will be back to stock kernel and recovery.
    3. To flash stuff or do backups/restore, use this temporary CWM that was compiled by me: Temp_CWM6.zip. Since I compiled it using our device's kernel code, it should be more stable than the temporary touch recovery, and the labeling of partitions are correct too...;)
    14
    Finally, after the long wait, v8 is here!!! And I have added stuffs that most of you will like ----> governors and schedulers!!! :D Download links in first post...;)

    Changelog:
    - Samsung CHN_JB_Opensource_Update1 (everything should be smoother & SODs are unlikely to occur)
    - Reduced size of zImage
    - Optimised memcpy and memmove
    - Updated CWM to 6.0.3.1 and TWRP to 2.5
    - Patched /dev/random
    - Added governors: HYPER, Scary, wheatley, abyssplug, minmax, interactiveX, lulzactive, lazy, pegasusq, lagfree, smartassV2
    - Added schedulers: vr, sio, row
    - Compiled using O3 flag
    11
    v5 is out!!!

    Ok guys, after lots of of testing and debugging by the community and myself, v5 is out now...it should be more stable and supports init.d+touchscreen fix...:)...for more info about updates, please refer the second post or my git hub...

    For those facing SOD again, if you wanna make a bug report, please state what were you doing before that happened, if possible, attached a log generated by lager...logs after a reboot are not relevant as it gets reset after a reboot...

    For those more adventurous ones, you can try this test build:

    Download: Blazing_Kernel_test1.zip

    It might further reduce SODs and random reboots (used configurations from CM, hopefully it works, works well for me so far)...and as usual please provide helpful feedback...;)...whining is strictly not welcomed here...

    So guys, enjoy (hopefully)...and this kernel update also signifies the upcoming of something else...:p