@Phil love the new recovery background mate. Thanks

Sent from my Sweet ROM powered GT-N7100

I've used kernel LT5 5.03.00 without problem.
I specially like Aroma File Manager in recovery mode. It's an excellent tool for modding when thing doesn't work.
Thank so much Philz !

Originally Posted by ahhl

@Philz
i think theres still random reboot bug in 5.03.0. i am on Sandroid Rom, but the reboot not as frequent as 5.00.0. i switch to speedmod , since yesterday, have not expericence any random reboot. so far

+1 Same here.

I got a bootloop right after I flashed "PhilZ-cwm6-XXLT4-OXA-5.00.5-signed" on stock XXLT4.
Don't know what to do now. Unplugged the battery and waiting.
Actually this happnes to me whenever i flash a Philz Kernel. It does not matter wheter it is bootloop fixed or not.
I have got bootloop all the time.
It is sad

---------- Post added at 01:30 PM ---------- Previous post was at 01:00 PM ----------

After reboot problem, I flashed Stock XXLT4 again.
But now it gets stuck on GT-N7000 Logo

Please help. What should i do?

Safest way is to flash 4 parts kl8 with repartition and pit file via odin first and then update ota

sent with samsung galaxy note

Originally Posted by aureldoku

Safest way is to flash 4 parts kl8 with repartition and pit file via odin first and then update ota

sent with samsung galaxy note

I did Nandroid restore and it worked.
But what is the reason for getting in a bootloop cycle even with a fixed kernel

---------- Post added at 04:33 PM ---------- Previous post was at 04:05 PM ----------

One way or anotheri I would like to install XXLT4. But ofcourse wanna avoid any possible bootloop problem again.

Sooo, what would happen if i never boot the Philz kernel but just the recovery to be able to flash another kernel.zip?
Is this idea dummy and born dead since booting into Philz recovery would already result in booting kernel together with its all parts, the one causing bootloop?

TIA

Originally Posted by ardicli2000

I did Nandroid restore and it worked.
But what is the reason for getting in a bootloop cycle even with a fixed kernel

---------- Post added at 04:33 PM ---------- Previous post was at 04:05 PM ----------

One way or anotheri I would like to install XXLT4. But ofcourse wanna avoid any possible bootloop problem again.

Sooo, what would happen if i never boot the Philz kernel but just the recovery to be able to flash another kernel.zip?
Is this idea dummy and born dead since booting into Philz recovery would already result in booting kernel together with its all parts, the one causing bootloop?

TIA

the bootloop bug is the friendliest bug, dont be scared to meet it from time to time......its easy to walk out of it...bit annoying thats all

when you change the kernel, recovery changes with it too

Originally Posted by rraaka

the bootloop bug is the friendliest bug, dont be scared to meet it from time to time......its easy to walk out of it...bit annoying thats all

when you change the kernel, recovery changes with it too

How come friendliest???
The only way to get rid of it is restoring your Nandroid Backup. Reverting back to old times. This is not friendly to me at all.

And when you have it ocne you can't solve it. That's the main problem. If I were able to boot I would immediately flash other kernel. But no chance

this bug has been here for ages

since the very first JB leaks came out

enough solutions have been written

you always have a choice