Database Develop

ROM Manger: Is it needed? (Anymore)

Its a great program and all. I however dont flash roms. All I do is just update my kernel, I use one of existz's kernels. Anyway, I use Quickboot to boot into recovery to flash new kernels, and it seems to work fine. Recovery is Recovery, right? I've read a few things about SGS Kernel flasher, but have also read it can cause some issues.

The only reason I could ever see for ROM manager would be if you lost your copy of CWM.
Sent from my SAMSUNG-SGH-I897 using XDA App

rom manager is only good for getting CWM onto your stock rom

So I should keep it? Just wondering. Trying to get rid of unused crap on my phone.

The only problem I've had with Kernel Flasher is getting in a hurry and forgetting to disable my lagfix (guar anteed bootloop).

I see. Ive never disabled it with CWM through ROM Manager. Am I supposed too?

i dunno what/where he was coming from talking about kernel flasher.
we were talking about rom manager...
if your kernel has CWM built in you do not need Rom Manager and the update.zip file.
CWM is BUILT IN to the kernel.
so if you dont need it get rid of it.

Oh. Ok...ya I dont rename anything to update.zip anymore. Let me read and see if that kernel has CWM

you dont normally rename anything. in rom manager the first button is download CWM. it downloads update.zip to your root SDcard directory and it uses that to "re-install package" from 2e 3e recovery. if you never see 2e/3e recovery anymore your kernel is probably CWM. what kernel are you using?

I use existz Captivate Kernel #8 lol. I don't think it has another name.

ConeyKiller said:
Its a great program and all. I however dont flash roms. All I do is just update my kernel, I use one of existz's kernels. Anyway, I use Quickboot to boot into recovery to flash new kernels, and it seems to work fine. Recovery is Recovery, right? I've read a few things about SGS Kernel flasher, but have also read it can cause some issues.
Click to expand...
Click to collapse
Op said he didn't like kernel flasher. Thought I would throw that out since he said all he wanted to do was flash a new kernel.

I have it. I never use it.

[Q] Read alot, can someone please confirm I am doing this right.|RESOLVED|

Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Thanks to all who responded, if anyone else wants to reply feel free but i'm going to mark this as resolved so their won't be any confusion.

amd-dude said:
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Click to expand...
Click to collapse
if you are on stock kernel then download Philz kernel for LP7, flash that in recovery, should give you root again aswell. then you can flash away to any of the ROMs you listed above. just every time you flash a ROM or think of factory reset or data wiping make SURE you're on a SAFE kernel. that's all

as you are rooted, just install any safe kernel like hydracore or philz. thats all. then you can try out any rom. Just make sure you follow the instruction to flash the rom in the OP

I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?

amd-dude said:
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
Click to expand...
Click to collapse
this is the one you use - PhilZ-cwm6-UBLPC-UUB-2.7
http://www.mediafire.com/file/35d4kd...2.7-signed.zip

the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it

nokiamodeln91 said:
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
Click to expand...
Click to collapse
First, forget about the franco kernel. The franco kernel for the Note is outdated and thus useless. Second, if you plan to flash a JB leak the only kernel you should use is PhilZ. And especially important with the JB leaks is to stick exactly to the instructions how to flash. Otherwise your phone won't even boot.
Have fun with your device! The Note is still an outstanding phone.
Sent from my revived Galaxy Note

Thanks guys for the quick replies, i'm gonna flash the philz kernel now and give the leaked version of JB a try.

make nandroid backup 1st..

[Q] MaxFu_HydraCoreNirvana_n3.JBT_STD.zip

Hi All,
I'm newly registered as I have problem in using HydraCoreNirvana Kernel.
I was using ZSLPN ICS Stock ROM with PhilZ-cwm6-ZSLPN-OZS-v2.7 Kernel.
A few days ago, I booted into CWM (Power + Up + Home) to flash MaxFu_HydraCoreNirana_n3_std.zip kernel.
HydraCore Kernel is working fine except that this kernel uses a lot of battery according to the
battery monitor. I keep using it for 3 days to make sure the whole system is stable after flashing a new kernel
but it is still consuming a lot of power.
Today, I boot into CWM (Power + Up + Home) to flash back the PhilZ-cwm6-ZSLPN-OZS-v2.7.zip kernel.
After flashing, I select reboot system, the "Galaxy Note N-7000" shows up and then black screen, i.e. without
the boot animation screen. I wait for a long time but still black screen. I tried to power up serveral times but same
thing happen. I then boot into CWM (Power + Up + Home), I can see PhilZ CWM so the PhilZ kernel should be flashed.
I then use this PhilZ CWM to flash Hydra kernel again and then reboot system. It can boot up.
I then try to boot into CWM to flash PhilZ kernel again, same problem. Now I flash back to MaxFU_HydraCoreNirana Kernel.
What's wrong with my procedures? Any idea? Now, I'm afraid to flash any other kernel as I am afraid I cannot flash
back to MaxFu Kernel and that will brick my phone.
Please help. Thank you so much.
I cannot post in Max_FU kernel thread as I am new here and not allowed to post there.
http://forum.xda-developers.com/showthread.php?t=2053084
Thanks.

It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.

To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99

dbolivar said:
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
Click to expand...
Click to collapse
Thank you so much for the detailed description. I've not noticed that Mail drivers are being installed.

zai89 said:
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
Click to expand...
Click to collapse
Hi zai89, thank you so much for your file. I flashed it and then I can flash back to PhilZ newest version.
By the way, I have used your file (v5.3 std kernel) for a while and it consumes the power normally. I still don't
understand why the HydraCoreNirvana drains huge power in my ROM (of course I am not complaining about
HydraCoreNirvana kernel, maybe my ROM problem). Since now I can flash back to PhilZ kernel, I may try
the v5.3 standard you suggested and see how good it is.
Once again, thank you very much for your time and kindly help.

[Q] Help flashing the right kernel

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!

How To Flash Tangerine Kernel Or DooMLoRD Kernal Without Phone Data Losing ??

I need to flash Tangerine Kernel Or DooMLoRD Kernal.. one time i test. but my all data erased. i want flash one of kernal without data losing.. Please Can you Help Me ?
Stock 12.1.A.1.205
JellyBean 4.3
C5303

KoRTaN said:
I need to flash Tangerine Kernel Or DooMLoRD Kernal.. one time i test. but my all data erased. i want flash one of kernal without data losing.. Please Can you Help Me ?
Stock 12.1.A.1.205
JellyBean 4.3
C5303
Click to expand...
Click to collapse
Tangerine only works for Lollipop roms so don't even try it or you be stuck in a bootloop, Doom kernel I think it's too old, try Williams Kernel 9.1, best one for 4.3 roms. Did you unlock your bootloader?

HUEguy said:
Tangerine only works for Lollipop roms so don't even try it or you be stuck in a bootloop, Doom kernel I think it's too old, try Williams Kernel 9.1, best one for 4.3 roms. Did you unlock your bootloader?
Click to expand...
Click to collapse
Stock 12.1.A.1.205 / C5303 / JellyBean 4.3 / Bootloader Unlocked / Rooted
Can I Flash Williams Kernel 9.1 Without Any data losing (auto wipe data\chache) or bootloop error ??

KoRTaN said:
Stock 12.1.A.1.205 / C5303 / JellyBean 4.3 / Bootloader Unlocked / Rooted
Can I Flash Williams Kernel 9.1 Without Any data losing (auto wipe data\chache) or bootloop error ??
Click to expand...
Click to collapse
Flashing a kernel doesn't auto wipe data. Since you're completely stock right now, I am guessing you'll be flashing the kernel via fastboot so you should be fine. As for boot loop errors, the kernel's meant for stock based roms so it shouldn't be a problem. I remember using it with Existenz. Worse case scenario, you'll have to reflash the kernel part from the stock firmware with Flashtool if things go wrong. Alternatively you could take a backup of your kernel via Rashr since you're already rooted.
Speaking of Rashr, you could use it to flash a recovery in your Fota partition which doesn't go away unless and until you remove it using stock firmware. This means that no matter which kernel or rom you flash, you'll always have a working recovery to get yourself out of trouble. You can take a complete nandroid backup of your system before even trying Williams kernel and in the off chance your phone is stuck in a bootloop, you can just restore your nandroid backup and you'll be back to stock.
If you're still worried about your data, just get Titanium backup and make a backup before you proceed. I have switched over a dozen roms in the past few months only because of it. Imagine setting up 30-40 apps every time you migrate to a different rom

XenolithicYardZone said:
Flashing a kernel doesn't auto wipe data. Since you're completely stock right now, I am guessing you'll be flashing the kernel via fastboot so you should be fine. As for boot loop errors, the kernel's meant for stock based roms so it shouldn't be a problem. I remember using it with Existenz. Worse case scenario, you'll have to reflash the kernel part from the stock firmware with Flashtool if things go wrong. Alternatively you could take a backup of your kernel via Rashr since you're already rooted.
Speaking of Rashr, you could use it to flash a recovery in your Fota partition which doesn't go away unless and until you remove it using stock firmware. This means that no matter which kernel or rom you flash, you'll always have a working recovery to get yourself out of trouble. You can take a complete nandroid backup of your system before even trying Williams kernel and in the off chance your phone is stuck in a bootloop, you can just restore your nandroid backup and you'll be back to stock.
If you're still worried about your data, just get Titanium backup and make a backup before you proceed. I have switched over a dozen roms in the past few months only because of it. Imagine setting up 30-40 apps every time you migrate to a different rom
Click to expand...
Click to collapse
Thanks For Details And i need to know, How to flash recovery & kernal ?
Kernal Can speedup my XSP ?

KoRTaN said:
Thanks For Details And i need to know, How to flash recovery & kernal ?
Kernal Can speedup my XSP ?
Click to expand...
Click to collapse
If I am not mistaken, SP like most older Xperia phones (not sure about the new ones) does not have a stock recovery nor does it have a recovery partition. The recovery is part of the kernel (the boot.img file or the .elf file). So when you flash a kernel, you are flashing the recovery along with it. This is why people flash a recovery in the Fota kernel partition since its a separate partition and is not overwritten while flashing other roms or kernels. A recovery flashed in the fota partition becomes your primary and only visible recovery irrespective of how many recoveries came bundled with the kernel you flashed. The only way to remove it is by flashing stock firmware or to be more specific, the fota kernel from the stock firmware. If you need it, you can find it here :
http://forum.xda-developers.com/showpost.php?p=59908442
Now since your phone's already unlocked and rooted, go grab Rashr from the playstore and use it to flash the latest Twrp from here :
http://forum.xda-developers.com/showpost.php?p=61698751
This way you will have a permanent recovery which you can use to take a nandroid backup before you try new roms or kernels and restore it if things go wrong.
Your other option is to flash the kernel via fastboot but remember if you flash another rom, the existing kernel will be overwritten by the kernel that came with the rom. It becomes really cumbersome when you are trying different roms. Another reason to flash a recovery in the Fota partition.
As for a new kernel speeding things up, yeah it helps. The first link is also the main thread for Tangerine kernel which has CPU overclocking and governor options and a bunch of other tweaks to improve performance but its only for LP roms. If you wanna stay stock, you can try the Williams kernel. Doesn't have as many features as the Tangerine kernel but more than the stock kernel. If you know which tweaks to make, I am sure you can gain a performance boost from either.