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

[musashiro]

its normal for the not to flicker when battery is at 2 or 3 percent. happens on stock kernel as well. I don't know of it will really solve you issue.

is that so? i never experienced that on stock... maybe because i don't stay on stock kernel that long..

either way, my hydracore kernel is outdated and i plan on trying this kernel since i loved cfroot (its my very first rooted kernel on s2) and mainly because this kernel is SO popular,,,


thanks for the heads up...

 

[eybee1970]

Please post your bug issued and doubts on the kernel thread so I can follow it easier. Things are fast here.
Again, I test on lsj jb leak for i9100 and updates, nandroids, full restored from and to jb were tested and do work without issued.
The patching doesnt cause other issues on i9100. N7000 and i9100 are much same.
Wiping cannot leave traces of my kernel after you flash a full rom, it is a big non sense.
Either it is a poor leak (which I sm sure) or the deodexing added by modded rom causes issues like it was with black crash...

I am open to contributive debugging on the kernel thread. Link in signature.

Sent from my GT-I9100 using Tapatalk 2

Thx Phil,

I did not have a single issue til now...just reacting on what shoey was experiencing and it sounded quite reasonable to me...I guess he didn't mean traces of your kernel are left, but parts of ROM not being wiped....let's see...about deodexing: maybe, but I never heard of it before bringing up issues - which doesn't mean anything of course

 

[rraaka]

is that so? i never experienced that on stock... maybe because i don't stay on stock kernel that long..

either way, my hydracore kernel is outdated and i plan on trying this kernel since i loved cfroot (its my very first rooted kernel on s2) and mainly because this kernel is SO popular,,,


thanks for the heads up...

Musa, you should try Phills kernel and recovery but its roms like LRT LR9 LS7 and others too that have the latest recovery. LRQ was a good rom and its kernel is equally good but not the latest.

 

[shoey63]

@Phil3759. CLOSE THE POLL! JB kernels are SAFE! I just did wipes and formats on stock JB using the lethal CWM.zip (The same one one that bricked my phone some months ago) It seems Samsung's patch + your patch don't work together. So for JB you can release unpatched kernels with your ever improving recovery:beer:

Sent from my GT-N7000 using xda app-developers app

 

[rraaka]

@Phil3759. CLOSE THE POLL! JB kernels are SAFE! I just did wipes and formats on stock JB using the lethal CWM.zip (The same one one that bricked my phone some months ago) It seems Samsung's patch + your patch don't work together. So for JB you can release unpatched kernels with your ever improving recovery:beer:

Sent from my GT-N7000 using xda app-developers app

Incredible !
Looks like we've come one full circle.

 

[eybee1970]

@Phil3759. CLOSE THE POLL! JB kernels are SAFE! I just did wipes and formats on stock JB using the lethal CWM.zip (The same one one that bricked my phone some months ago) It seems Samsung's patch + your patch don't work together. So for JB you can release unpatched kernels with your ever improving recovery:beer:

Sent from my GT-N7000 using xda app-developers app

does this really prove 'brickfree'?
AFAIK it could happen on your 1001st wipe even if it doesn't 1000 times before...or am i wrong?

Hope I am wrong..

 

[musashiro]

does this really prove 'brickfree'?
AFAIK it could happen on your 1001st wipe even if it doesn't 1000 times before...or am i wrong?

Hope I am wrong..

+1.. i do believe that it could happen anytime...

 

[dsmas]

Dear Philz, I am using your kernel since started flashing jb roms. Earlier speedmod for ics. Now I read about leftovers and lost+found files. Always I do clean formats and wiping before flashing any rom with your kernel. Now does that means there will be still some leftovers. Thanks if you could Clarify.

Sent from my GT-N7000 using xda premium

 

[shoey63]

does this really prove 'brickfree'?
AFAIK it could happen on your 1001st wipe even if it doesn't 1000 times before...or am i wrong?

Hope I am wrong..

What it proves is that JB kernel does not accept "secure erase" commands. In ICS, you will get an instant superbrick.

Sent from my GT-N7000 using xda app-developers app

 

[eybee1970]

What it proves is that JB kernel does not accept "secure erase" commands. In ICS, you will get an instant superbrick.

Sent from my GT-N7000 using xda app-developers app

ok, now I got it. Thx.

 

[rraaka]

its ironical that ICS is right now SAFER than JB,

why ? coz we made it so
so we will find a way out of this too

i know as a community we will never grow out of the brick syndrome

but

what is the worst that could happen in the present set up- bootloop, stuck on sam logo ? and it doesnt happen with all zip files ! eybees supercharger script worked fine, vincent's mod zip file worked fine, raj's and xepriacles zip installed well, but i got stuck with the transparent flashbar zip, and wiping dalvik and cache didnt work, i had to power off and on and i was into the rom again, fine

i didnt vote on the poll because we really dont have a choice ....yet

 

[Phil3759]

I think that jb is safe but even the xda dev elites cannot ensure it. Until source release we are stuck. Also once jb is official, the number of users will grow and we get a better feedback until source is released

The past showed that early leaks were killers in that regard

On i9100 we got a better finished jb leak and there are 0 issues of this type for 3.62, 3.65 and now the new 3.70 I just released this night.

Most suppositories here are with very low evidence and sadly not having a note makes it impossible for me to test. Most users report no issues on lsa too.

My kernels do not add any extra driver or script in other partitions. That means they cannot persist if you do wipe fully. Now, the patching could bug it but it is not the case for i9100 and most n7000 users.

The poll now tends to continue patching especially by most known contributers...

Sent from my GT-I9100 using Tapatalk 2

 

[Phil3759]

Add to my above post, can some one post about the issue he has with exact details he did? Only reports related to full stock rom installed are considered. The full rom should include a data and system partition + csc and cache + kernel. That is when flashed in odin a full wipe

Sent from my GT-I9100 using Tapatalk 2

 

[AndroidSlave]

Most suppositories here are with very low evidence

 

[eybee1970]

I think that jb is safe but even the xda dev elites cannot ensure it. Until source release we are stuck. Also once jb is official, the number of users will grow and we get a better feedback until source is released

The past showed that early leaks were killers in that regard

On i9100 we got a better finished jb leak and there are 0 issues of this type for 3.62, 3.65 and now the new 3.70 I just released this night.

Most suppositories here are with very low evidence and sadly not having a note makes it impossible for me to test. Most users report no issues on lsa too.

My kernels do not add any extra driver or script in other partitions. That means they cannot persist if you do wipe fully. Now, the patching could bug it but it is not the case for i9100 and most n7000 users.

The poll now tends to continue patching especially by most known contributers...

Sent from my GT-I9100 using Tapatalk 2

ok, fully agree...but maybe it is possible to give people the choice between 'unpatched' and 'patched'? But it is your decision and I go with all of them

 

[Phil3759]

ok, fully agree...but maybe it is possible to give people the choice between 'unpatched' and 'patched'? But it is your decision and I go with all of them

People who want to go in depth into things can just flash samsung stock one and keep it. They will only miss the recovery and some + features like custom-bootanim, init.d...
No one needs my kernel to be rooted, there are some root methods from stock recovery in my signature

If they are happy after a few days on stock samsung and can say that after these honeymoon days on stock they flashed mine and on reboot they got a bootloop or what ever issue, than we can look at it deeper.

I just cannot fix something no one reports here in detail so that I can try to reproduce on my phone.

Note: excuse my last typing errors, I hate default JB keyboard.

 

[eybee1970]

People who want to go in depth into things can just flash samsung stock one and keep it. They will only miss the recovery and some + features like custom-bootanim, init.d...
No one needs my kernel to be rooted, there are some root methods from stock recovery in my signature

If they are happy after a few days on stock samsung and can say that after these honeymoon days on stock they flashed mine and on reboot they got a bootloop or what ever issue, than we can look at it deeper.

I just cannot fix something no one reports here in detail so that I can try to reproduce on my phone.

Note: excuse my last typing errors, I hate default JB keyboard.

yes, I don't have an issue, so I can report nothing...next user reportng strange things in my thread, I will send here!
I would like to have unpatched prerooted, because:

- permanent CWM recovery
- init.d-support (mainly for SuperCharger not possible without)

Bootanim I don't care...I like my phone booted permanently and not having to reboot for watching nice bootanim :laugh:

 

[Phil3759]

yes, I don't have an issue, so I can report nothing...next user reportng strange things in my thread, I will send here!
I would like to have unpatched prerooted, because:

- permanent CWM recovery
- init.d-support (mainly for SuperCharger not possible without)

Bootanim I don't care...I like my phone booted permanently and not havong to reboot for watching nice bootanim :laugh:

I can build a non patched kernel for you with last recovery, you distribute with proper warnings if you like?

By the way, I read many complaining 3.60 or 3.62 was better than 3.65...
Only thing they miss: these are exactly all same kernels. I no longer edited the kernel part since a while now. Only working on recovery

 

[eybee1970]

I can build a non patched kernel for you with last recovery, you distribute with proper warnings if you like?

By the way, I read many complaining 3.60 or 3.62 was better than 3.65...
Only thing they miss: these are exactly all same kernels. I no longer edited the kernel part since a while now. Only working on recovery

ok, I can distribute with 100 warnings, all in oversized and bold red...but you can do also...but I am ok with it!
Yes, I heard about it...tbh, I still use 3.62 coming with your first LSA and I did not feel the need to change it

 

[Phil3759]

ok, I can distribute with 100 warnings, all in oversized and bold red...but you can do also...but I am ok with it!
Yes, I heard about it...tbh, I still use 3.62 coming with your first LSA and I did not feel the need to change it

I do advise 3.65 as it comes with many fixes for the recovery. ORS support is broken on previous builds and mainly, that version could have some missing permissions on some recovery files

That way, you can tell me if just flashing 3.65 will turn you in a bootloop