[PhilZ-cwm6][n7000] Stock Kernel+CWM6+Root+exFAT+NTFS-LTA

[Phil3759]

Ghokanmoral and some kernel devs over the i9100 suspected the following:
- with latest JB ROMs, /data partition gets corrupted on unexpected shutdown
- changing the init binary with older ones will let the system boot even if /data is corrupted
- some ROMs seem immune to the issue, what ever kernel/init binary combo is used
- changing the init, will not fix the /data corruption issue
- many parts were suspected like bootloader, some binaries related to toolbox..., none showed to be the reason

The only person I know that can give a definite explanation for this is Ghokanmoral , but his dev over the i9100 is for now on hold because of personal reasons

In my case, using an older JB ROM with latest kernels, repacked or stock, will make all reboots work. Using any newer ROM with a non repacked kernel will stuck in the bootloop

I sadly have no time at all to focus on this. As I said, I stick to stock kernels and I do not plan any soon to start compiling kernels from source. I only focus on coding for CWM and maintaining ramdisk changes for the kernel whenever it is needed or a fix proven to be effective

 

[nokiamodeln91]

I lost the custom settings on Touch recovery like the menu color, preload in nandroid, brightness etc after flashing the new kernel though.

 

[Phil3759]

I lost the custom settings on Touch recovery like the menu color, preload in nandroid, brightness etc after flashing the new kernel though.

You missed 4th line in change log
http://forum.xda-developers.com/showpost.php?p=40406321&postcount=3139

If you did a backup once, it should have restored things on next reboot
However, you can still just move the settings folder from /system to /data and your lost backups will resuscitate

 

[nokiamodeln91]

oops sorry..

 

[zai89]

So, next built will keep the original binaries, or use the older one just like before?..

 

[Phil3759]

So, next built will keep the original binaries, or use the older one just like before?..

You decide...
For now it is a mixed deal
But probably revert to old binary so that it is ok for all, except hotboot which will be buggy it seems...

 

[majdinj]

Since I don't know what is the concept of immune device means... Just curious whether deleting philz-touch folder from system partition will solve others problem!!

 

[Phil3759]

Since I don't know what is the concept of immune device means... Just curious whether deleting philz-touch folder from system partition will solve others problem!!

No, this has nothing to do. The issue is present on a stock ROM/kernel combo freshly installed in odin
It is Samsung crapware. At least my kernel lets you boot and run your ROM while Sammy will die in a bootloop

 

[zai89]

for hot reboot, I can use 3rd party apps..
for bootloop bug, I will choose philz kernel..

 

[Tassos_i]

What a shame !!!

Just installed latest OXALT4_DBT through PC Odin after cleaning everything twice. Guess what ? Before rooting or installing anything new, after initial start, pressing the power button for 7 secs leads to ...BOOTLOOP (the full one)! Back to XXLSZ stock rom with semi-bootlooping Philz 4.93.6XXLSZ kernel.

EDIT (off topic) : I kept the new XXLT3 modem though, which seems to work very nice.

 

[Formhault]

Since the old binaries seem to fix the bootloop bug (in any way possible), and do not affect stability or functionality (right?)... I'd suggest you stick with those, Phil.

What do the new binaries add...? The bootloop bug, here and there. Besides that, no increased functionality etc...

 

[majdinj]

So technically, the problem is triggered when you flash stock official rom with odin then flashing new philz kernel, right?? since I am on custom kernel and new philz kernel is working without any drop of problem!!!

 

[Phil3759]

So technically, the problem is triggered when you flash stock official rom with odin then flashing new philz kernel, right?? since I am on custom kernel and new philz kernel is working without any drop of problem!!!

No
Read what I wrote: It is a Samsung issue. PhilZ kernel = Samsung kernel
No need to flash anything else than Samsung great files to be stuck in the bootloop

 

[Formhault]

So... in other words... FU Samsuck.

We wanted this OTA so much... they gave it to us, but not in the form we were expecting it (no black clipping fix, not all Note 2 features ported as we were told... bootloop bug...).

@Phil : keep the previous inits that resolved the bootloop. Apparently, you alone are better than Samsung's entire dev team. And I think we can all agree on this one. Most XDA devs are better than some OEM's devs, I guess. Either that, either it's juuuuuust marketing .

 

[majdinj]

No
Read what I wrote: It is a Samsung issue. PhilZ kernel = Samsung kernel
No need to flash anything else than Samsung great files to be stuck in the bootloop

So if I understand correctly, that means if you use old JB release with this new philz kernel it will be alright?? (sorry for being lazy brain!!)

I am on custom deodexed JPLSB, with PhilZ-cwm6-JPLSB-UAE-4.93.6-signed installed with philz_installer.cfg toggle to skip installing SuperSU..

I want to help since I don't have those problems that others have..

 

[whitedavidp]

Philz For Release LT4?

I have noted on Sammobile that there is an LT4 release of 4.1.2 for my Note I. Still no idea what is changed on it from the LSZ I am currently running. Is there a Philz safe kernel with root for this? Thanks

 

[Formhault]

Funny. LT4 ROM with LT3 modem...

Sent from hyperspace

 

[Phil3759]

So if I understand correctly, that means if you use old JB release with this new philz kernel it will be alright?? (sorry for being lazy brain!!)

I am on custom deodexed JPLSB, with PhilZ-cwm6-JPLSB-UAE-4.93.6-signed installed with philz_installer.cfg toggle to skip installing SuperSU..

I want to help since I don't have those problems that others have..

Well, then maybe your custom Deodexed ROM fixed something. I doubt the kernel is fixed.
Only LS2 ROM I think was fine for N7000, that is really an old leak one

 

[Klementiy]

**

 

[Phil3759]

is, of course, here it is http://forum.xda-developers.com/showpost.php?p=40478707&postcount=3200

I have no problem that you repack them, but just do not name them as if they were mine.
Or at least mention that these are repacked by you, so Non Official PhilZ-cwm6 releases

I will release LT4 and release all previous versions with fixed init as soon as I am done supporting new HTC devices