• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEVELOPMENT] SickleKernels For the SV

simonsimons34 said:
I'll add in color control if the kernel is controllable, cpu freq and all the settings that every other Dev charges for. I want to give a free solution to users with no special animations, something that just does its job. But I also want to give good looks so I may create a donate app too eventually
Click to expand...

Hey is there a way to flash this kernel without A computer cause mine isn't working right now and I want to try this kernel out.
 
JohanToGood said:
I am s-off.
Click to expand...

Place it on your sdcard, name it boot.img for simplicity, then open up the terminal emulator on your device. Insure your system is writable.

Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20

or

Code: 
cat /sdcard/boot.img > /dev/block/mmcblk0p20

PLEASE take note that "/dev/block/mmcblk0p20" is the boot partition for the K2_CL, K2_UL, K2_U and K2_PLC_CL devices - to prevent any confusion amongst other readers.
 
ModdingMyMind said:
Place it on your sdcard, name it boot.img for simplicity, then open up the terminal emulator on your device. Insure your system is writable.

Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20

or

Code: 
cat /sdcard/boot.img > /dev/block/mmcblk0p20

PLEASE take note that "/dev/block/mmcblk0p20" is the boot partition for the K2_CL, K2_UL, K2_U and K2_PLC_CL devices - to prevent any confusion amongst other readers.
Click to expand...

Thank you Modding. I have the K2_CL :D
 
ModdingMyMind said:
Place it on your sdcard, name it boot.img for simplicity, then open up the terminal emulator on your device. Insure your system is writable.

Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20

or

Code: 
cat /sdcard/boot.img > /dev/block/mmcblk0p20

PLEASE take note that "/dev/block/mmcblk0p20" is the boot partition for the K2_CL, K2_UL, K2_U and K2_PLC_CL devices - to prevent any confusion amongst other readers.
Click to expand...

xD lol after I did this I rebooted. it soft bricked and I forgot to make a back up.
 
ModdingMyMind said:
Place it on your sdcard, name it boot.img for simplicity, then open up the terminal emulator on your device. Insure your system is writable.

Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20

or

Code: 
cat /sdcard/boot.img > /dev/block/mmcblk0p20

PLEASE take note that "/dev/block/mmcblk0p20" is the boot partition for the K2_CL, K2_UL, K2_U and K2_PLC_CL devices - to prevent any confusion amongst other readers.
Click to expand...

ok i fix it using my friends computer and doing [HIGH]fastboot flash boot awesomeandroid422boot.img[/HIGH]
 
Please never use the cat method. That can be very dangerous in certain circumstances. Always use dd or busybox dd
 
dd is just as dangerous as using cat. Heck, most pros know dd by the infamous nickname, disk destroyer. It got that nickname for a reason ;-). So whether using dd or cat, common sense should always apply and by insuring you don't make a typo depending on how you go about using them.
 
ModdingMyMind said:
dd is just as dangerous as using cat. Heck, most pros know dd by the infamous nickname, disk destroyer. It got that nickname for a reason ;-). So whether using dd or cat, common sense should always apply and by insuring you don't make a typo depending on how you go about using them.
Click to expand...
Dd is made for the use :) always use the right tool for the job
 
JohanToGood said:
Hey guys since I flashed the new awesomeboot422 I have not been able to use nfc is there any way to fix that
Click to expand...

So THAT'S the reason. I was trying to figure out why my nfc randomly broke, but restoring my stock backup fixed it... If this is indeed the case, i would assume someone would have to recompile the kernel with whatever fixes were needed to get it working. Short of that, there's not much you can do but restore the stock kernel.
 
The kernel provided by shinru (misspelled?) was based on the cricket variant but modified to work with boost. That would explain the bug(s). Definitely recommend using the kernel source strictly for the K2_CL. I will be picking up my laptop today so maybe I can grab the source and compile it. Depends on how late it is when I get off of work. Also busy dealing with GraphicsMagick and my current toolchain. The configure file in the source is making it difficult to pick up on some Libs such as png for example. Got to fix this before I do anything else on my end.
 
Great!Up to now ,there is no kernel that supports s2w for cricket or boost phones(4.2.2).will you add this fonction?
 
Working on building the source now.

36201ce8cd75332068ee4281bac29d74.jpg
 
Disregard, the source has some issues. Puts phone in bootloop.

Simonsimons34, just so you are aware, when running:
Code: 
make clean && make mrproper

The source pops up with some errors.

make[2]: *** No rule to make target '/kernel_source/drivers/gud/Makefile'. Stop.

make[1]: *** [drivers/gud] Error 2

make: *** [_clean_drivers] Error 2
Click to expand...

Kernel source puts phone in to a bootloop unfortunately. I will look at the source in hopes to resolve the problem. Meanwhile, wanting to let you know.
 
I compiled the source using the arm-linux-gnueabi toolchain if that is of any importance :-).
 
I use linaro armeabi. Also that make error is normal
Also get a dmesg
 
simonsimons34 said:
I use linaro armeabi. Also that make error is normal
Also get a dmesg
Click to expand...
Yea, the source builds without problems. But at the end of the day it still boot loops. To confirm it wasn't my unmkbootimg and mkbootimg I handled a stock boot.img and all went well. So, definitely something going on with the kernel lol. I noticed it is missing some directories as well.
 
I'm gonna go ahead and clone my source. My linux got wiped out earlier lol. Will build off of that for now and post it here.
 
You must log in or register to reply here.
Back
Top Bottom