Database Develop

[ODIN][N8013]Stock Kernel and Recovery Images

This post will contain N8013 stock kernel and recovery images. For UEALGB these were dumped from a device that was rooted using the "root injection of /system" approach. For UEALH2, they are simply extracted from the Kies dump at http://forum.xda-developers.com/showthread.php?t=1847706 so that you can get a stock kernel or recovery without downloading 1GB of files.
If you flash any of these using Odin, they should not trigger your flash counter. Note that for some reason, flashing these in Heimdall will trigger the counter (unlike Heimdall on most other devices).

Pardon for some ignorance. What should be the steps to follow in order to root from an updated to latest OTA update stock Rom on a 32gb USA version? Do I need to flash the kernel, or just recovery should be ok?
Sent from my SAMSUNG-SGH-I717 using xda premium

sgndroid1 said:
Pardon for some ignorance. What should be the steps to follow in order to root from an updated to latest OTA update stock Rom on a 32gb USA version? Do I need to flash the kernel, or just recovery should be ok?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Why don't u ask this in the root thread?
Here is what you should do:
Root Via CWM (method 2 in the root thread)
1. Download and put the superuserzip on your internal memory on your device
2. In odin uncheck auto reboot and load the cwmrecovery tar in the pda slot
3. Start odin
4. Once finished boot directly into clockwork (volume up and power til the samsung screen then let go of power while holding volume up)
5. Use the volume rockers to scroll in clockwork cause its finicky and flash the superuser zip you put on your device.
6. reboot
7. Make sure you have root and touch screen and pen works
8. Download goo manager
9. In goo manager hit menu and hit the install recovery script
10. DONE
Have any problems odin back to a stock image and if things go bad flash entropys triangle away kernel and clear your binary count

Any chance you could update the thread to account for the updated kernel for the N8013, that adds support for exFAT?

NessLookAlike said:
Any chance you could update the thread to account for the updated kernel for the N8013, that adds support for exFAT?
Click to expand...
Click to collapse
Um it is here the H2 one

BeerChameleon said:
Um it is here the H2 one
Click to expand...
Click to collapse
..now I feel embarassed.. :silly:

I have tried to flash the stock UEALGB recovery tar from Mobil Odin and every time it says partition could not be found in file, any ideas?
Sent from my GT-N8013 using xda premium

Hey guys,I just picked up a GT-N8010 -Canadian Wifi version - running LG4 firrmware, will any of these stock recoveries work for me or do I need an LG4 recovery?
Looking to root via cwm then restore stock recovery so I can receive OTA's.

Android564 said:
Hey guys,I just picked up a GT-N8010 -Canadian Wifi version - running LG4 firrmware, will any of these stock recoveries work for me or do I need an LG4 recovery?
Looking to root via cwm then restore stock recovery so I can receive OTA's.
Click to expand...
Click to collapse
For OTAs - no, these will probably not work.

Ok I downloaded the UEALGB stock recovery tar again and it contains only boot.img. Is the link bad or am I just screwy?
Sent from my GT-N8013 using xda premium

Thanks Entropy, as much as I want to root now I am going to wait for either a stock LG4 recovery or a root injected LG4.
Sent from my GT-N8010 using xda app-developers app

Android564 said:
Hey guys,I just picked up a GT-N8010 -Canadian Wifi version - running LG4 firrmware, will any of these stock recoveries work for me or do I need an LG4 recovery?
Looking to root via cwm then restore stock recovery so I can receive OTA's.
Click to expand...
Click to collapse
I have the Canadian 8010 model, and installed the prerooted firmware that was provided. It didnt flash right the first time but the second time it did. Everything works great and Im rooted with CWM. The only thing I noticed is that it says I have the 8013 model now which is probably because of the firmware but its not a big deal.

Robert542 said:
Ok I downloaded the UEALGB stock recovery tar again and it contains only boot.img. Is the link bad or am I just screwy?
Sent from my GT-N8013 using xda premium
Click to expand...
Click to collapse
Crud, I probably uploaded the wrong thing. Will look into this.

Robert542 said:
Ok I downloaded the UEALGB stock recovery tar again and it contains only boot.img. Is the link bad or am I just screwy?
Sent from my GT-N8013 using xda premium
Click to expand...
Click to collapse
It still only has boot.img.
Does anyone have a working UEALGB stock recovery?

Please, update the LGB recovery. I think that's the kernel.
Can I flash the H2 recovery in a LGB rom??
Cheers!

el_charlie said:
Please, update the LGB recovery. I think that's the kernel.
Can I flash the H2 recovery in a LGB rom??
Cheers!
Click to expand...
Click to collapse
You can't, but you can flash the entire H2 ODIN image from here (about 1GB):
http://forum.xda-developers.com/showthread.php?t=1847706
and not lose your data. You lose root though (which you can get again through the alternate recovery method)

Can we get a kernel and recovery from UEALI3 please.

Can someone dump latest firmware please and pm me.
Sent from my GT-N7000 using Tapatalk 2

Anybody have stock recovery for N8010?

N8013 UEALI3 Recovery
Can anyone post the UEALI3 stock recovery? I want to root my Note, but want to root my Note with the CWM method, and go back to stock recovery so I can get OTA updates.
Thank you.

***WARNING***Recovery & Kernel in ICS***HARDBRICK-WARNING***

Dont use wipe, restore,or factory reset in STOCK ICS kernel with your Recovery
Thank you for moderator make this sticky..
You know that this not new for us.. This problem exist in many samsung devices with ICS, i got this brick on my GT-N7000 and my device had a motherboard replacement because of that, and it seem our beloved tab definitely got this problem too..
im no dev..just an ordinary Windows and Unix User,not Using English as my Native
but I will update and summarize the issues in this thread until we got the fix about it..
If you already in ICS you need to read the whole thread from this to figure out what the problem is..
Emmc bugs is exist.. And if you need to know what kind of EMMC you have and the possibilty of brick, use this app from chainfire
This is suspected kernel and recovery build from ICS source with this bug if you try to wipe on this:
-any boot.img from stock ICS
-any recovery.img from stock ICS
-CWM 6.0.1.2 which is build from ICS source..
-update binary which is build from ICS source..
Click to expand...
Click to collapse
Discussion about this:
CWM 6.0.1.2-Risk of Brick start by fred_be9300 please report your issue about CWM here..
Official CM9 thread by kallt_kaffe , discussion about this start from page 107
Click to expand...
Click to collapse
After you read, this is my advice:
Dont use any wipe operation or something similar with that such as:
command "Format" in Edify script if you plan make a flashable zip
Nandroid Restore in CWM (build from ics source)
Using wipe with stock recovery in stock ICS boot.img(kernel)
Wiping in safe CWM in stock ICS boot.img
using wipe and nandroid restore with CWM from ICS source without mmc erase patch
using update-binary from ICS build..(compiled from ICS source without mmc erase patch)
Click to expand...
Click to collapse
Thanks for entropy512 who figure out this and make all samsung users more aware about flashing in ICS
And chainfire who makes the tools..
This is not about what version of cwm are used.. But what kind of kernel that recovery operates..
If the recovery execute the command in honeycomb kernel maybe its more safe then ICS kernel..
This is quote from chainfire itself
Chainfire said:
..... CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android....
Click to expand...
Click to collapse
this is possible solution if you want to flash, wipe or restore in ICS
First method: use recovery.img and boot.img with MMC_CAP_ERASE disable.. For that you must familiar with compiling kernel from the source..
Second method:Flashing recovery.img and boot.img from honeycomb, after installation done reboot to recovery and flash the ROM you desire..Remember, your ROM package must have boot.img and recovery.img too..
Click to expand...
Click to collapse
PLEASE BE CAREFULL UNTIL SOMEONE WITH MORE KNOWLEDGE SOLVE THIS FOR US..REMEMBER ITS JUST A WARNING! WHATEVER YOU DID, YOU OWN THAT RISK!!!
Some people are able to safely wipe and flash using affected kernels forever. Some people can wipe a few times before problems occur, some people have problems on their first wipe.
The number of people that broken kernels affect may only be 5-10% - but so far, there is no way to definitively determine that you are safe without putting your device at risk.
Click to expand...
Click to collapse

nandroid restore....are you serious?

orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Yep. And some zip file update-binary executables too (the edify format() function in the 'updater-script's).
Specifically those update-binary commands that were statically linked with the ICS version of the ext4 library.
Both of these operations (edify format() and nandroid partition restore) make use of the make_ext4fs() function. That function apparently changed in ICS to add a call to the eMMC erase functionality in the vigilant pursuit of security. However, that functionality is what tickles the eMMC fw bug with the 'bad' kernels (i.e. those that don't have the erase functionality disabled).
Oh what a tangled web we weave ...

Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium

Jnn1 said:
This should work, right?
Click to expand...
Click to collapse
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.

orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Nandroid restore is ONLY unsafe in a recovery that (itself) is built with a buggy ICS kernel. Version 6.0.0.8 and before are safe, because based on earlier GB kernel.
Also, update-binary (a copy of which exists in EVERY flashable zip) is ONLY unsafe IF built against buggy ICS kernel module... and if the updater-script in the same zip does a format()
I don't know if we've already seen dangerous update-binary in the wild... Mostly people don't recompile that, but endlessly reuse older ones. Still, you might want to check that next time you want to flash a zip. Or keep a safe update-binary available to inject into any zip you want to flash...
Disclaimer: this is my interpretation based on careful reading of many posts

This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8

pseudoheld said:
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
Click to expand...
Click to collapse
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.

kallt_kaffe said:
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
Click to expand...
Click to collapse
Haha yeah you did it was in the cm9 thread as a test version. I had it running quite some time without any problems but decided to be on the safe side with 6.0.0.8

It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.

fred_be9300 said:
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
Click to expand...
Click to collapse
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.

tracid said:
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
Click to expand...
Click to collapse
Oh well, then they are safe. I just didn't notice the version number had changed. Only the 6.0.1.2 version has the dangerous kernel.

So again...
1. I have the same eMMC chip revision number known to be brickable as per Chainfire's app.
2. I have been using CWM 5.5.0.4 only and never anything else.
3. I have flashed CM9 and AOSP Jelly Bean without bricking my device using CWM 5.5.0.4
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Again, I am only asking for an assumption, not a definitive answer. Will hold nobody responsible.

de3pkeeper said:
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Click to expand...
Click to collapse
should be safe!
it seems like only in conjunction with the newer cwm the brick can happen.

boscorama said:
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
Click to expand...
Click to collapse
Ah ... I see ... the recovery has it's own kernel that is a separate beast from the Rom kernel ... thanks for taking the time to kindly explain! And I'll make sure to stay on cwm 6.0.0.8 or lower!
Sent from my GT-P7310 using xda premium

Jnn1 said:
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes you can..
We dont know from what kernel the bugs appear maybe from boot.img or from recovery.img..
So the safest way is flash the safe boot.img with safe recovery.img in one flashable.zip and then reboot to recovery again and flash the ROM you desire..
It works and tested by me..

There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks

nexus_g said:
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
Click to expand...
Click to collapse
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.

boscorama said:
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
Click to expand...
Click to collapse
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.

notz76 said:
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
Click to expand...
Click to collapse
The important thing here is what you used to install CM9.

[Q] [Help] Stuck At Boot When Try To Root Using PhilZ Recovery !

Hello everyone. I'm a newbie samsung user. I tried to root my phone (N700-Galaxy Note - ICS 4.0.4) using PhilZ Recovery method:
http://forum.xda-developers.com/showthread.php?t=1901191
When I flash the zip in the stock recovery, everything seems to be ok, then when I got out and pressed "Reboot System now", the phone just turned off. I tried to power it on, but I stuck at the N7000 Logo (the logo just appears for a few seconds then disappears). However, I can still access the PhilZ Recovery
What should I do now? Should I flash a new rom with new kernel using that recovery (e.g: OmniRom with Raw Kernel)?
Please help, I'm really worry :crying:

Since you have Philz kernel then you can flash any TW ROM or AOSP ROM which is not KitKat. If you want to try out KitKat then you would have to first flash Raw Kernel and then from Raw kernel you can flash KitKat (ex. OmniROM).
If you want to go back to stock then you would have to flash a stock ROM using Odin.

whats the name of the zip file you flashed?

nokiamodeln91 said:
whats the name of the zip file you flashed?
Click to expand...
Click to collapse
This file:http://d-h.st/users/philz_touch/?fld_id=16061#files
Did you flash it too? Do you encounter that problem like me ?

XperiAwesome said:
This file:http://d-h.st/users/philz_touch/?fld_id=16061#files
Did you flash it too? Do you encounter that problem like me ?
Click to expand...
Click to collapse
come on! you need to be more specific about the link you gave. it opens a can of kernels.

nokiamodeln91 said:
come on! you need to be more specific about the link you gave. it opens a can of kernels.
Click to expand...
Click to collapse
I don't think he has to be more specific, all of those kernels are for JB 
 @XperiAwesome flash an ICS Philz Kernel

SOLVED [Q] Please Help! Soft Bricked Gt-N7000 stuck in boot loop

Hello, i recently tried to flash the C-Rom on my gt n7000, but i keep getting the tmp/sideload/package.zip (status 7) error, now my phone is stuck in bootloop. i read that i need to flash a stock rom but my charging port has been damaged as such i cant connect the phone to my computer to use Odin. Is there a stock rom that can be flashed through recovery?

annie22 said:
Hello, i recently tried to flash the C-Rom on my gt n7000, but i keep getting the tmp/sideload/package.zip (status 7) error, now my phone is stuck in bootloop. i read that i need to flash a stock rom but my charging port has been damaged as such i cant connect the phone to my computer to use Odin. Is there a stock rom that can be flashed through recovery?
Click to expand...
Click to collapse
You came so far, its to late to turn back...
If only you had read the instructions...
Then you would know...
That you need a more recent version of your recovery...
Which is part of a kernel...
So flash raw kernel...
And then flash C-Rom...

annie22 said:
Hello, i recently tried to flash the C-Rom on my gt n7000, but i keep getting the tmp/sideload/package.zip (status 7) error, now my phone is stuck in bootloop. i read that i need to flash a stock rom but my charging port has been damaged as such i cant connect the phone to my computer to use Odin. Is there a stock rom that can be flashed through recovery?
Click to expand...
Click to collapse
To Flash ANY/ALL KK Based Roms (4.4+) you need base recovery 0f 6.0.4.4+. Can you still reboot to recovery? What rom vers are you previously on? Rooted? What recovery? If your charging port has been damaged, how are you gonna charge your phone? Get it repaired ASAP before doing anything else. Loss of battery during Rom flashing can make your phone a nice desk decoration.

Jackwu696 said:
To Flash ANY/ALL KK Based Roms (4.4+) you need base recovery 0f 6.0.4.4+. Can you still reboot to recovery? What rom vers are you previously on? Rooted? What recovery? If your charging port has been damaged, how are you gonna charge your phone? Get it repaired ASAP before doing anything else. Loss of battery during Rom flashing can make your phone a nice desk decoration.
Click to expand...
Click to collapse
Yes i can boot to recovery, thats all my phone does is load with the Samsung boot logo then the recovery screen. Im on the offical samsung stock rom. Yes its rooted.CWM, I use a universal battery charger, the battery was full before i tried flasing the C-Rom.

annie22 said:
Yes i can boot to recovery, thats all my phone does is load with the Samsung boot logo then the recovery screen. Im on the offical samsung stock rom. Yes its rooted.CWM, I use a universal battery charger, the battery was full before i tried flasing the C-Rom.
Click to expand...
Click to collapse
Do you still remember your Stock Rom's Build number? If yes, then you can try downloading philz safe kernel with recovery that is compatible with your build number, flash it in cwm recovery, then reboot to RECOVERY, from there do a factory reset wipe, all formats (system, data, cache, preload) wipe dalvik cache (If you don't understand any of the terms I mentioned above, please go to philz page and read) and Flash a TW BASED custom rom first (you can find and download any rom as long as it's TW based). See if that boots.
Ultimately you WILL need that charging/USB Port fixed so please make that a TOP Priority

Azeazezar said:
You came so far, its to late to turn back...
If only you had read the instructions...
Then you would know...
That you need a more recent version of your recovery...
Which is part of a kernel...
So flash raw kernel...
And then flash C-Rom...
Click to expand...
Click to collapse
I read the entire C-ROM tutorial, before doing anything.

Jackwu696 said:
Do you still remember your Stock Rom's Build number? If yes, then you can try downloading philz safe kernel with recovery that is compatible with your build number, flash it in cwm recovery, then reboot to RECOVERY, from there do a factory reset wipe, all formats (system, data, cache, preload) wipe dalvik cache (If you don't understand any of the terms I mentioned above, please go to philz page and read) and Flash a TW BASED custom rom first (you can find and download any rom as long as it's TW based). See if that boots.
Ultimately you WILL need that charging/USB Port fixed so please make that a TOP Priority
Click to expand...
Click to collapse
No i dont remember it...

annie22 said:
No i dont remember it...
Click to expand...
Click to collapse
Then I suggest you fix that port so you can use odin, otherwise follow @Azeazezar advice

annie22 said:
I read the entire C-ROM tutorial, before doing anything.
Click to expand...
Click to collapse
Follow these instructions.

Azeazezar said:
Follow these instructions.
Click to expand...
Click to collapse
Ohh, , okay will do.

@annie22 you could also download any JB kernel (if you were on JB) of philz and flash it in recovery, reboot recovery, then flash Raw kernel r4 or r5 and reboot recovery and from there flash C-Rom or any other KK rom. You can use any philz kernel irrespective of the build number as long as you are using it only to flash another kernel and then rom of your choice. Make sure to download the .zip version of the philz kernel and put that and raw kernel and rom on external sd card. Keep back up of these kernels and roms on pc as well so that you can connect memory card to pc and transfer those files back to card, as it so happened that i while doing full wipe on philz kernel it also wiped my external card.

treacherous_hawk said:
@annie22 you could also download any JB kernel (if you were on JB) of philz and flash it in recovery, reboot recovery, then flash Raw kernel r4 or r5 and reboot recovery and from there flash C-Rom or any other KK rom. You can use any philz kernel irrespective of the build number as long as you are using it only to flash another kernel and then rom of your choice. Make sure to download the .zip version of the philz kernel and put that and raw kernel and rom on external sd card. Keep back up of these kernels and roms on pc as well so that you can connect memory card to pc and transfer those files back to card, as it so happened that i while doing full wipe on philz kernel it also wiped my external card.
Click to expand...
Click to collapse
Hi, thanks. Excuse my slowness but Umm could you direct me to the link please, I've been searching and feel I'm going around in circles, I see the thread for philz but no download link..

annie22 said:
Hi, thanks. Excuse my slowness but Umm could you direct me to the link please, I've been searching and feel I'm going around in circles, I see the thread for philz but no download link..
Click to expand...
Click to collapse
You should be able to flash raw kernel from just about any custom recovery. Just skip philz

Azeazezar said:
You should be able to flash raw kernel from just about any custom recovery. Just skip philz
Click to expand...
Click to collapse
Problem is, both r4 n r5 download links are dead... do u know any mirror? I'd like to keep a copy of r5 too just in case I need TWRP.
Sent from my GT-N7000 using XDA Free mobile app

Jackwu696 said:
Problem is, both r4 n r5 download links are dead... do u know any mirror? I'd like to keep a copy of r5 too just in case I need TWRP.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
The links work fine here.
If you have trouble I could send you a copy.

Azeazezar said:
The links work fine here.
If you have trouble I could send you a copy.
Click to expand...
Click to collapse
Yes I'd really like that mate. Gonna DL it 1st thing tomorrow. Just the raw5 will do. Thanks again for your trouble
Sent from my GT-N7000 using XDA Free mobile app

annie22 said:
Hi, thanks. Excuse my slowness but Umm could you direct me to the link please, I've been searching and feel I'm going around in circles, I see the thread for philz but no download link..
Click to expand...
Click to collapse
Can't search, Can't help.

annie22 said:
Hi, thanks. Excuse my slowness but Umm could you direct me to the link please, I've been searching and feel I'm going around in circles, I see the thread for philz but no download link..
Click to expand...
Click to collapse
if you r on cwm based or any custom recovery
goto android development page download forest cm11 kernel and flash it have latest philz recovery
if you are on stock
then
got original android development page >philz*******>download odin flashable md5> flash>install forestcm11 kernel> install c rom or any other
i dont know why u people search for single when you have an alternate
thanks to @forest1971

Flash success!!!! Bricked no more.
Just wanted to say thank you to everyone for all the advice, I was finally able to flash the philz jb kernel and then install the latest version, then iinstall C rom. YAAAAAY!!!!!! Phone is now fully functional

annie22 said:
Just wanted to say thank you to everyone for all the advice, I was finally able to flash the philz jb kernel and then install the latest version, then iinstall C rom. YAAAAAY!!!!!! Phone is now fully functional
Click to expand...
Click to collapse
Glad to hear that, Remember to change your thread by adding [SOLVED] to let others know and also as reference to others facing the same problem.
---------- Post added at 07:14 AM ---------- Previous post was at 07:14 AM ----------
annie22 said:
Just wanted to say thank you to everyone for all the advice, I was finally able to flash the philz jb kernel and then install the latest version, then iinstall C rom. YAAAAAY!!!!!! Phone is now fully functional
Click to expand...
Click to collapse
Glad to hear that, Remember to change your thread title by adding [SOLVED] to let others know and also as reference to others facing the same problem.

[Q] CM11 + CWM on GT-N7000

Hi Guys. short (and maybe dumb) question but i have to be sure before messing up the phone of my friend.
I would like to flash CM11 nightlies with clockworkmod on a Samsung Galaxy Note GT-N7000.
I have read several tutorials for flashing the GT-N7000 and i'm not sure which is the best way to do it.
It is neccesary to update or change the (current stock) kernel? Or is it possible to just copy the recovery and ROM to the SD card, boot into download mode, install from there?
Sorry i only have experience with flashing my HTC One X.
Thanks in advance,
Greetings

I am in the same possition. A friend of mine wants to help him install a custom rom to his n7000.
He has the stock samsung rom and the phone is LAGGY!!
I only have experience with flashing cm11 to my own galaxy s3 with philz touch recovery.
I am reading for 4 hours now and i am lost...
Should i only use TWRP?
but twrp has a version only for cm 10...(i havent found by searching any cm11 twrp version for n7000)
Should i use cm 10 then and all is ok??
Thanks a lot

I am reading things about installing kernel for recovery (philz touch)
After installing that, its just wipe data / cache and install Rom from Zip.
Im still bit confused about the rooting process -> Trough Zip or trough Odin.
I hope some1 can help me.

First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.

User_99 said:
First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.
Click to expand...
Click to collapse
Stock rom is currently installed. I uploaded a picture with the specs within an attachment

Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....

User_99 said:
Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....
Click to expand...
Click to collapse
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?

hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
you also need gapps

eveles said:
you also need gapps (and maybe for later use one custom kernel )
Click to expand...
Click to collapse
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?

hosseltietjes1990 said:
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?
Click to expand...
Click to collapse
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
Restore instructions :
I don't know if CWM recovery takes he same path to backup as Philz recovery but if it does it pretty simple
- just reboot to recovery and do the steps a to d from the above installation steps and restore backup
But in case you are not able to find backup file in CWM then do this
- reboot to recovery
- flash Philz kernel (same one you flashed during installation )
-go to advanced and select "reboot recovery"
- now you should be in Philz recovery again
- do steps from a to d again and restore
Simple
REVENGE SOLVES EVERYTHING

tysonraylee said:
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!

hosseltietjes1990 said:
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!
Click to expand...
Click to collapse
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
oh and btw let me tell you that recovery and kernel are in the same partition for N7000 so you can't have "this kernel and that recovery" here as you would in other devices. Thus if you need a certain recovery then you have to flash a certain kernel and if you need a certain kernel then it will install the recovery that comes with it overwriting the previous one. Also even if you flash just recovery somehow, the device will restore the one with the kernel upon reboot
So yeah
REVENGE SOLVES EVERYTHING

tysonraylee said:
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
I just recently flashed my HTC one X And the One X of a friend of mine. No need there to flash the kernel on that phone, only recovery trough adb and flash rom. So i really dont wanna mess with kernels
I you would like to ask something, feel free to ask! Thanks for the support

hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
The kernel code name should match the currently installed TW rom (4.1.2) or should it match the CM11 rom you intend to flash (4.4.4)????
to answer my own question : In XxPixX's quide of course it says r5 so 4.4.4 )
Anyway the kernel that you have downloaded is neither r5 nor r1 (i beleive that r1 is for 4.1)
Thanks, i hope someone with more experiense would clarify that!!

eveles said:
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
thanks!!!!!!
Click to expand...
Click to collapse
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
the kernel code name should match the ROM (4.1.2) the one you currently have. Download the philz JB kernel for your JB ROM(follow the steps given in philz kernel thread)
There is no requirement as such for 4.4.4 ROM
REVENGE SOLVES EVERYTHING

tysonraylee said:
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000

hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
The download link you have provided links to r6 not r5
r6 says that is only for omniron 4.4
We were talking about cm11.

eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
Oh i'm sorry haha. R6 should work right?
edit: sorry i did not read properly. r5 it is then

hosseltietjes1990 said:
Oh i'm sorry haha. R6 should work right?
Click to expand...
Click to collapse
No.
r5 should work.
Dude you are more confused than i am!!

hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
yes that should do it, download the k44 one
I haven't seen any videos about that but it is possible to do so but that's just using the recovery temporarily to flash a certain ROM but in the end that recovery is replaced by the ROMs kernel recovery its the same thing we are doing by using raw kernel here in these installation steps but its true that it gets a little confusing
I have updated my previous reply. Please refresh the page to see the explanation
eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
R6 is the latest version. Please download the R6-k44.zip
REVENGE SOLVES EVERYTHING