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

[chasmodo]

Well rraaka couldn't post because it was more than 8 mb. (No doubt due to extra recovery features). Anyway I have original stock from Chasmodo and will test soon.

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

Sorry, but it's not stock kernel that I have sent you. It's extracted from PhilZ', I thought that was what you were after.

Sent from Nexus 7

 

[sitanshu91]

I have rooted stock Indian rom lr9 using philz kernel v 2.7
Now I want to unroot ....can anyone guide me on this?

Sent from my GT-N7000 using xda premium

 

[milsabords]

I have rooted stock Indian rom lr9 using philz kernel v 2.7
Now I want to unroot ....can anyone guide me on this?

Sent from my GT-N7000 using xda premium

There is an Unroot function in Super SU/Settings. Also Philz has posted a Busybox uninstaller in this thread.
I have not tested either of them.

 

[shoey63]

Sorry, but it's not stock kernel that I have sent you. It's extracted from PhilZ', I thought that was what you were after.

Sent from Nexus 7

Yes I just noticed. I was hoping for pure stock withouth Philz recovery. Thanks for trying though. Anyway I think I have identified the problem. N7000 kernel partition is exactly 8mb. Trying to flash anything larger won't work. The "quick release" Phil3759 put out for devs to incorporate into their ROMs is smaller, hence no issues. Latest Philz LSA kernel is bigger than 8mb so users are having problems when they flash on top of LSA ROM. Just my opinion though...

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

 

[rraaka]

makes sense to me shoey

there are requests for stock kernel at the lsa thread by others......


look !!!


http://forum.xda-developers.com/showpost.php?p=34528320&postcount=348

is it 100 % safe to use with Phills temp recovery ?

 

[Phil3759]

Well rraaka couldn't post because it was more than 8 mb. (No doubt due to extra recovery features). Anyway I have original stock from Chasmodo and will test soon.
Edit 3.62 LS7 is 7.9 mb whereas LSA is 8.2
Sent from my GT-N7000 using xda app-developers app

I see
Starting of these leaks, the zImage is now sized exactly as full partition. It was alway some bytes less up to ICS
It won't make any difference in normal conditions.
By the way, for i9100 it is still undersized for the stock kernel and have same size as in ICS

Anyway, this has 0 impact

 

[shoey63]

makes sense to me shoey

there are requests for stock kernel at the lsa thread by others......


look !!!


http://forum.xda-developers.com/showpost.php?p=34528320&postcount=348

is it 100 % safe to use with Phills temp recovery ?

Ok thanks. Will download and check

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

 

[Phil3759]

Yes I just noticed. I was hoping for pure stock withouth Philz recovery. Thanks for trying though. Anyway I think I have identified the problem. N7000 kernel partition is exactly 8mb. Trying to flash anything larger won't work. The "quick release" Phil3759 put out for devs to incorporate into their ROMs is smaller, hence no issues. Latest Philz LSA kernel is bigger than 8mb so users are having problems when they flash on top of LSA ROM. Just my opinion though...

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

Wrong

Stock is: 8'388'608B
PhilZ: 8'387'840B

I always used that size, same as used by Samsung. Only LSA and LS7 are now padded up to full size
I will padd to full size and post. There is a small footprint in stock zImages that could persist and cause issue in some circumstances
Maybe people migrating from LS7 to LSA first experience the bug

Wait a few mn for an update test

 

[Phil3759]

Well,

here's a small update that only padds the zImage to full size
Since sammy changed their zImage size with these N7000 JB builds, it could be... I suspect th eJB leaks for N7000 are done on a some hurry. LS7 included even a build.prop in /sbin... JB leak for i9100 still has same standard zImage size...

I am more and more tempted to ignore next n7000 leaks... until they fix their things

Anyway, Please do the following before reporting any issue with my kernel:

• FULL WIPE before updating to LSA. Yes, do it or do not post issues
• Flash stock leak and than update with this new kernel: http://www.mediafire.com/file/497l2jz9kby43mu/PhilZ-cwm6-XXLSA-XJB-3.63-signed.zip
• If any issue, try flashing the pure stock untouched one from here: http://forum.xda-developers.com/showpost.php?p=34528320&postcount=348
• You can flash the boot.img from inside my recovery. Just put it in sdcard under clockworkmod/.kernel_bak
• Now see if it fixes your issue
• Flash again my kernel, and see if issue is back
• AFTER ALL THAT: Report your issue in the kernel thread here

 

[shoey63]

Ok thanks. Just flashed stock LRA from eybee on LR7 and got BSOD. So it seems you are right. I will download LRA ROM and test tomorrow. (Saturday work again @ 7am again unfortunately)

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

 

[Phil3759]

Ok thanks. Just flashed stock LRA from eybee on LR7 and got BSOD. So it seems you are right. I will download LRA ROM and test tomorrow. (Saturday work again @ 7am again unfortunately)

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

Thank you for the confirmation :good:. You know, what I hate the most is when people do report issues with my kernel before comparing to stock one. I loose a lot of time, and actually, this is very frustrating
Since I cannot verify my self (no Note phone), I rely on people assumptions. Most do not even bother doing a wipe before flashing these leaks. By default they are full wipe. Could be modders remove the /data to avoid a full wipe, but you should really fully wipe before testing leaks. They are not optimized for updates at all, that's why they leak as wipe normally

edit: Sorry for your weekend. Have some events tomorrow too, so won't be updating or fixing

 

[Tassos_i]

Just flashed 3.63 on a clean lsa and it worked perfectly.

Sent from my GT-N7000 using Tapatalk 2

 

[Phil3759]

PLEASE READ BEFORE POSTING ABOUT ISSUES WITH LEAKED FIRMWARE:

A leaked firmware is not supposed to be flashed by noobs, it is risky and unstable
A leaked firmware is quiet always full wipe. If it is not, than probably modder / releaser removed the /data to avoid wipe: this is a bad step, just wipe before installing any leak, fully wipe
Leaked firmwares are unstable, especially early leaks. N7000 leaks are immature and being cleaned on each release. This is a fact


Now, most issues about bootloops, FC... are related either to a crappy leak, users flashing LSA kernel over LS7 ROM, people not doing a full wipe include /data before update, people restoring apps+data after install and finally people reporting issues after they used tons of custom early release mods/custom roms

I will stop further developing for N7000 leaks until people report things after testing in the order I mentioned above

Keep in mind, I do not have a Note and I never had one. So, I trustfully rely on people reports. If they say they wiped while they didn't and further reports show the opposite, I am just loosing hours looking at false problems

Now, if some one wants to be constructive, test following exact steps I mentioned and report with details. Any other reports such as it doesn't boot, it loops without detailed info from template... will not be looked at anymore

Instructions posted again and for the last time:

• FULL WIPE before updating to LSA. Yes, do it or do not post issues
• Flash stock leak and than update with this new kernel: http://www.mediafire.com/file/497l2jz9kby43mu/PhilZ-cwm6-XXLSA-XJB-3.63-signed.zip
• If any issue, try flashing the pure stock untouched one from here: http://forum.xda-developers.com/showpost.php?p=34528320&postcount=348
• You can flash the boot.img from inside my recovery. Just put it in sdcard under clockworkmod/.kernel_bak
• Now see if it fixes your issue
• Flash again my kernel, and see if issue is back
• AFTER ALL THAT: Report your issue here

After that, I could look to check if my repacking process is causing any issue

 

[shreeyashattal]

There is no ROM ddlr1, confirm again this should be baseband not kernel. Your build version will be DDLR9 and that is already availabloe.

as on 23.11.2012, samsung updated one to ddlr1

cant find a safe kernel for it; please update

 

[shoey63]

Yes indeed! For users information, unlike ICS kernels which are totally interchangeable, JB LSA kernel will NOT work on previous versions!

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

 

[clive48]

Hi
I am using N7000 with Baseband N7000DDLR1, Kernel 3.0.15_HydraCore_v4 & Build IMM76D.DDLR6. My N7000 is rooted.

Can I safely use below kernel :
PhilZ-cwm6-DDLR6-ODD-v2.7
http://www.mediafire.com/file/d5m87m...2.7-signed.zip
http://www.mediafire.com/file/4k4hkm...DD-2.7.tar.md5

Method :
Download xxx-signed.zip kernel matching your ROM
Put the previously downloaded xxx-signed.zip file on your external sd card
Boot into stock recovery (volume up+home+power)
Select "apply update from external storage".
Now select the xxx-signed.zip file you copied in previous step
You are rooted + new PhilZ-cwm6 kernel with CWM6

Pl confirm if this is safe & wont brivk my Note

Question 2 : Post this, Can I do JB 4.2 upgrade wout going back to Stock ROM?

 

[nokiamodeln91]

1. yes
2. going back to stock. rom? you already are on one. Anyway yes. you can flash any rom after flashing philz kernel.

Sent from my GT-N7000 using xda premium

 

[bangsti]

Sorry für OT.

Thank Phil for your work here and the great Kernel with all the Options.:good:
New 3.63 work perfect.

Greetings
bangsti

 

[shreeyashattal]

Where to find philz kernel to root ddlr1.. Coz I looked in the thread couldn't find one.. I could have missed.. Though unlikely..
Was on ddlr9 with philz cwm.. Updated ota and note root is gone..

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

 

[rraaka]

phill, i know lsa has been testing your patience

but please just consider, our phones wouldnt boot without your expertise

also thanks shoey for your intense involvement

and all those who gave feedback

(ive run out of thanks again )