Originally Posted by nail16

Brood i got it to work it's working perfectly with broodrom rc3 v2 with SKYhigh kernel v1.3, this time i flashed the boot.img using a script shell even the bootanimation plays

Thanks allot for your help . however i still get a hang at the boot logo.. and then after 10 sec reboot. I kinda thinking that the KP4 modem is the one that screws it up, im gonna test it with KQ1 modem now.

Also getting a hang with KQ1 Modem :S

and strangely every time it bootloops i get the battery charging logo instead of the samsung logo, but when i boot in recovery i get the right one :/

Think i have to reinstall my system completely

That maybe the problem cause i'm using rc3 v2 and it works fine, Strange but cool, when i reboot to recovery via the power menu the feacore logo appears (he sure knows how to take credit for his work lol)
I'll try flashing the KP4 Modem, just give me the link

Originally Posted by nail16

That maybe the problem cause i'm using rc3 v2 and it works fine, Strange but cool, when i reboot to recovery via the power menu the feacore logo appears (he sure knows how to take credit for his work lol)
I'll try flashing the KP4 Modem, just give me the link

Here is the modem file:
http://www.mediafire.com/?4davd59iwo1tqh8

and the feacore logo also appears in recovery.img :P so when booting in recovery you only see it ^^

XXKP4 Modem doesn't seem to be the problem the rom works fine along with the bootlogo
I know why it bootloops it's because of thunderbolt

Originally Posted by nail16

XXKP4 Modem doesn't seem to be the problem the rom works fine along with the bootlogo
I know why it bootloops it's because of thunderbolt

What does thunderbolt that the boot sequence doesn't like, Do you know that?

see i tried the new thunderblot v2.6.1 so i'll go through TB thread, might find some clues.
I feel it's some incompatibility between sky kernel and TB
skyhigh kernel was actually meant to be used with Cyanogenmod,
i'll make a logo cmw zip with feacore kernel.

It's some problem with skykernel, feacore kernel with the rc4 boot logo works fine.
It's confirmed skyhighkernel v1.3 with thunderbolt 2.6.1 & LMK addon results bootloop.

Originally Posted by FlorisNL

ok, clear. is it possible to change the SAMSUNG logo (the first one)?

Sent from my GT-I9001 using xda premium

Originally Posted by broodplank1337

I think not since I've never ever seen anyone that didn't had the original manufacturer logo. But I could be wrong

Actually it is possible, Samsung did it obviously
But the reason why you never saw it so far is quite easy as well:
trying this is one of the best methods to hard brick your phone and you must be mad to even try it !

Technically the logo is somewhere in the lower mmc blocks (mmcblk0p0-7) and the xda wiki tells you to never touch these. And there is a very good reason for this serious warning: YardE was bold enough to try it anyway and hard bricked his phone consequently although he is a developer and coder and usually knows what he is doing !
This should be warning enough for all of you here.

Originally Posted by broodplank1337

I think a customized boot logo / boot animation is plenty graphical customization for the boot sequence, implanting a boot logo isn't that easy also. (spent in total over 24 hours trying to get it working but still no success :X. I keep needing other people to fix it for me)

I totally agree on that

Originally Posted by nail16

It's some problem with skykernel, feacore kernel with the rc4 boot logo works fine.
It's confirmed skyhighkernel v1.3 with thunderbolt 2.6.1 & LMK addon results bootloop.

Explains why almost all custom boot.img files weren't working for me today
And thanks allot btw for making allot of boot.img files for me ^^

Originally Posted by skywalker01

Actually it is possible, Samsung did it obviously
But the reason why you never saw it so far is quite easy as well:
trying this is one of the best methods to hard brick your phone and you must be mad to even try it !

Technically the logo is somewhere in the lower mmc blocks (mmcblk0p0-7) and the xda wiki tells you to never touch these. And there is a very good reason for this serious warning: YardE was bold enough to try it anyway and hard bricked his phone consequently although he is a developer and coder and usually knows what he is doing !
This should be warning enough for all of you here.

If YardE bricks his phone it's serious business haha, i know i may never touch mmcblk0p0-7 I don't want to try since it can lead to hardbricks

Originally Posted by nail16

Brood don't you remember you have to dd zero first to get it working right
You don't need to mount
just do this in adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p8
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
reboot

sometimes you have to restart the phone after the dd zero step
wait i'll post some pictures

I have uploaded a cmw package

That's not right at all. Zeroing mmcblk0p8 is totally redundant and has cosmetic effects only. And slows down the process of flashing.
Therefore manveru0 removed this routine from his FeaMod update since V1.3

While it is right that mounting /system for flashing kernel is redundant it could be necessary to mount sdcard or emmc. This is mandatory for example when you flash the kernel in recovery mode. But you can also use the CWM menus then to mount

Originally Posted by nail16

now i'm really confused it's strange that i does'nt work for you
can it be the kernel?
i'll try editing a fresh new boot.img form feacore pheonix
what firmware are you on RC3 V2 ?
i analysed skywalkers boot image yesterday its the same only with the new logo intergrated.
did the older boot.img work for you?
lol look dude i ain't soo good at playing detective but i'll try my best to rectify this problem

That's right, I only exchanged the boot logo with a correctly converted version.

Originally Posted by nail16

XXKP4 Modem doesn't seem to be the problem the rom works fine along with the bootlogo
I know why it bootloops it's because of thunderbolt

In fact there is a high chance that Thunderbolt is the reason.

Originally Posted by broodplank1337

What does thunderbolt that the boot sequence doesn't like, Do you know that?

Pretty much everything !!! Thunderbolt, Adrenaline Shot and all tweaks like that directly interfere with kernel settings namely they change vital kernel settings in a running system. There is a nearly 100 per cent chance that this has more or less good or bad impact on the running system and the booting sequence as well. IMHO every developer and modder must know exactly what these tweaks do or otherwise MUST NOT use them !

They are meant for (modded) stock kernels only, developers and modders alike must port and test every single tweak for themselves if they want to use some of them.

That's exactly what I did, I already integrated a small amount of similar tweaks in SkyHigh 1.3, which have a high chance to be incompatible to certain Thunderbolt tweaks. It's the very same reason why Thunderbolt and Adrenaline Shot are NOT compatible !

Originally Posted by nail16

see i tried the new thunderblot v2.6.1 so i'll go through TB thread, might find some clues.
I feel it's some incompatibility between sky kernel and TB
skyhigh kernel was actually meant to be used with Cyanogenmod

Not this version, this is meant to be used with stock ROMs only. That means without kernel customizations by Thunderbolt because Thunderbolt won't work on a stock kernel anyway (no init.d support !) If you are using a stock kernel with init.d support please notice that this one is actually a modded kernel, a so called custom kernel and no stock kernel anymore !

And like I just answered in the CM port thread, SkyHigh is meant for use with plain stock ROMs only. This also means instead of stock kernel and with a plain unmodified stock system and so on. Chances to be incompatible with custom kernels and system tweaks - especially those in init.d - are rather high.

Originally Posted by nail16

It's some problem with skykernel, feacore kernel with the rc4 boot logo works fine.
It's confirmed skyhighkernel v1.3 with thunderbolt 2.6.1 & LMK addon results bootloop.

It's not a problem with SkyHigh kernel, it's a problem with throwing too much incompatible kernel and system tweaks into the same pot with actually not knowing what you are doing there. And FeaCore kernel works well because it hasn't integrated those tweaks. Just as I already said - SkyHigh has all the features of the latest FeaCore plus some own by myself. You just found some of the additional features, being rather performant without Thunderbolt but also being incompatible with it

To verify all of that try my attached boot.img, it works perfectly on stock ROMs without Thunderbolt and Adrenaline shot. Use it with your ROM with Thunderbolt (will most probably fail) and without (just rename init.d to something else before rebooting) and it should work flawlessly