I have an untouched Note running stock ICS 4.03 -- Kernel 3.0.15-N7000XXLPY ...). I'd like to be able to safely flash a custom ROM, avoiding the brick bug. I've been digging through a lot of threads, but some uncertainties remain.
Here's what I'm about to do: I'll get the Philz kernel matching my current rom (this would be PhilZ-cwm6-XXLPY-XEN-v3.99, right?), boot into stock recovery, flash the .zip from the sd card, and boom, I'll have a safe kernel with root and CWM to flash any ROM from. Is this about the right plan?
2 more specific questions:
1. The matching Philz kernel was posted under the headline "Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99" in the Philz kernel thread. But I'm running 4.03. So is this the right kernel for me?
2. Will the ROM I install after that have to match the Philz kernel in some way? I'm thinking of getting the Official CM 10.1 from the nightlies thread.
Thanks so much!!
That's the right plan
1. The correct rom is found under rom build which is the last in the section where you found the kernel version. The 4.0.4 also works with 4.0.3 so it's ok.
2. No the new rom will install a new kernel. Philz won't work with cm as philz is Samsung kernels repacked for safety and recovery..
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Correct me if I'm wrong but I don't think you can flash CM 10.1 from stock recovery.
Philz kernel comes with CWM recovery which provides more functionality than the stock recovery.
For example you can do a nandroid backup (basically a snapshot of your current phone system) so if you ever flash a rom that you don't like or something screws up, you can just restore your backup.
I think your first priority should just be flashing a safe kernel (Philz) and only then should you be looking into flashing custom roms.
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Custom rom can only be installed using Cwm
OK, thanks for your help guys. I just flashed the Philz kernel following to the instructions and all is well. CWM is working, and I appear to have root access in my old stock ROM.
But in the phone info, the kernel version is unchanged. It stil says: "3.0.15-N7000xxlpy-cl474507 [email protected] # 3 SMP PREEMT Fri May 4 04" -- which is the exac same thing it said before I flashed the kernel.
How can I verify if I'm actually running the safe Philz kernel now?
PhilZ Kernel are only modded kernel, so they aren't change and stock kernels. And so you won't see a description made by PhilZ but only the normal information of the original kernel.
To be sure: boot into recovery and check the CWM version and compare it with the infos in PhilZ thread.
But you told already that you do not have the stock recovery, so everything is ok.
Thanks ThaiDai. The fact that I had moved successfully from stock recovery to CWM was already a strong hint that things worked out.
I wanted to make extra sure, so before flashing the first custom ROM I went into CWM, made a backup of the stock samsung, and then took this script right here to examine the operating kernel (boot.img in the backup folder) for the brick bug: http://forum.xda-developers.com/showthread.php?t=1807995 -- the script returned that the kernel was safe.
So I went on to flash CM 10.1 and I'm a happy camper now! This forum is a great place for getting help, you guys are terrific!
Hello guys,
I would like to flash a different version of CWM onto my N7000 but somehow it does not stick.
I currently run AOKP 4.1.2 and it has 6.0.1.5 as CWM which always gives you the md5 generation error when you do a nandroid backup.
I've installed Rom Manager and downloaded a different version of CWM and tried to install it both with Rom manager and also in CWM itself.
On the first boot after I flash some other recovery like the one from rom Manager (6.0.1.2) it actually loads the new recovery and lets me do a sucessful nandroid for example, but when i reboot into recovery another time the old recovery is back.
When I flash a new rom though, the CWM does get permanently replaced. I flashed a different rom which came with CWM 6.0.2.8 and then I permanently had that version. (same behaviour when I tried to overwrite it with the 6.0.1.2, wouldnt stick).
I even tried just partially restoring the nandroid and leaving boot out, but then phone will get stuck on boot.
Is there any way to permanently flash a recovery to the note without overwriting the whole boot.img? CWM and Rom Manager do not seem to be able. Maybe Heimdall or ODIN? Been so long since I had to use them..
Hope someone knows whats goin on with the recoveries.?!
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
nokiamodeln91 said:
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
Click to expand...
Click to collapse
thanks man, yea i got some tools installed that should be able to do a nandroid from running system, was just wondering if there is a way to permanently switch the recovery - it is sometimes booted, right after flash but then its gone - so there must be a way to stop the restore or?
Or are there any custom aokp kernels out there for the n7000? usually they only support TW or CM as far as I saw, or only older versions.
how do I flash a new Booting.img though CWM... what I did was I made a backup of my custom rom then swapped the booting.img with new booting.img from withing my backup then flashed it but CWM said MD5 mismatch. Also tried flashing new booting.img in CMW advance options with no luck... how do I flash this guys?
Swapping files inside backup won't work at all. You need to create a custom update.zip with the boot.img you want to flash.
For what for you want to flash boot.img anyways? OC Kernel, stock rom, or something else?
oh right I see, so how do I create an update.zip for a custom kernal?
I think you can use the this update.zip which is originally a OC Kernel, and simply delete the one there, and insert your boot.img. I do not guarantee that this will work. Make a backup!
http://www43.zippyshare.com/v/24843785/file.html
The thing is I'm Dirty Unicorns 4.3.1 rom and your kernel has CWM only, do not like it for backups because I can not rename them. Only the kernel Doomlord has TWRP, which is only for stock. My question is can I just do the backup / restore with the kernel Doomlord and then use the original kernel to boot rom?
Hi, can anyone help me go back to cm 10.1 from cm 11. I already have the ROM and gapps. Need instructions thanks
download a cm 10.1 kernel from here: http://forum.xda-developers.com/showthread.php?p=29158659 (try the latest one)
flash kernel, reboot recovery and proceed with standard rom flashing