Related
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.
Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks
status 7 is usally a bad download / corrupted file, I think you should redownload it and check the md5 before flashing.
Also, flash over a full wipe (safe kernel obviously ) and see how it goes, As for the green jpg message, I believe thats the charging animation, So long as the phone is charging i wouldnt worry too much, Its probably been corrupted inside the ROM, so flashing a new one *could* replace the dodgy jpg image. :good:
what is the name of the file you downloaded for PA? are you getting this error ? assert failed: getprop("ro.product.device")
try a different kernel. The phone might not boot with that but you can install a new rom from recovery
Hello
I had your problem before, I found out it is a bad download (corrupted file)
First, I would like to explain that (EMMC) means the zip files i located on your internal storage
Status 7 can mean either you're using a version not optimized for your phone (so be sure you're downloading from N7000 forums) or it is a corrupted file
To conclude that, do a checksum on the zip file on your phone (There's a free app on play store called Checksum) and compare the checksum that is generated by the app to the checmsum on Utacka thread.. if they differ, then re-download the file from the forum (& repeat the checksum check before you flash it)
Best of luck
irgendeinname said:
Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks
Click to expand...
Click to collapse
Try flash Abyss kernel first and from Abyss kernel flash the paranoid android. It happened to me and it turns out not the rom is not corrected but I cannot flash directly from the Phil kernel.
irgendeinname said:
...emmc.. status 7 install abort.
Click to expand...
Click to collapse
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.
Hello,
I've the same problem like u.
Currently I'm still on ultimate 4.1.2 v5 which based on LSA. Everytime I tried to flash another ROM...the emmc status 7 error will appear.
So I guess we have similar problem.
To all expert guys here,
So if I installed the hydracore kernel and reboot to recovery, I can directly flash any new ROM that I want to flash?
Coz, last night my friend said by opening the zip file and edit the updater script on ro.build prop will help me to solved this status 7 error..but after i tried to reedit that script. It won't work. I still got that issue.
Let me try this method by flashing this HC kernel tonight..n i'll update u what I get. Btw I can use any kind of HC kernel right? Or I must use the latest version...which mean the version 7...
Regards
Sent from my GT-N7000 using Tapatalk 2
Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC
nokiamodeln91 said:
Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC
Click to expand...
Click to collapse
What do u mean with preload files?
Is it these one?
- zip rom file
- hc kernel
Are there any other files do i need to prepare before flashing that kernel?
Sent from my GT-N7000 using Tapatalk 2
Yes. Rom file and gapps file of cm rom. And hydracore
nokiamodeln91 said:
Yes. Rom file and gapps file of cm rom. And hydracore
Click to expand...
Click to collapse
Ok
Thx for ur help
Sent from my GT-N7000 using Tapatalk 2
Thanks
chasmodo said:
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.
Click to expand...
Click to collapse
Worked for me. Your a reassuring voice in forums. Now off to try CM10.1!
Thanks
New to me AHD will not boot into any custom roms, I'm confused as to why. But here's what I've done:
Root (motochopper)
Unlock bootloader
Using mythtools, flashed recovery
enter recovery, factory reset, also format /system (CWM Touch 6.0.4.4)
flash CM and Gapps
Afterwards, phone just sits at boot logo. I used mythtools to reflash stock firmware, and that boots and works fine, but when I repeat the process of flashing recovery and flashing a rom, the phone will no longer boot. What am I misssing?
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
quasihellfish said:
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
Click to expand...
Click to collapse
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
mustafu said:
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
Click to expand...
Click to collapse
M8 should work. It's still JB bootloader compatible.
palmbeach05 said:
M8 should work. It's still JB bootloader compatible.
Click to expand...
Click to collapse
Same goes with validus 6.0
It's like fastboot isn't working...keep trying to flash recovery from it and it doesn't seem to work. Going to check those threads.
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Which recovery are you using?
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
bylithium said:
Which recovery are you using?
Click to expand...
Click to collapse
CWM Touch 6.0.4.4
quasihellfish said:
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
Click to expand...
Click to collapse
Thank you, will give it a try.
mustafu said:
CWM Touch 6.0.4.4
Thank you, will give it a try.
Click to expand...
Click to collapse
I recommend philz. What rom are you flashing?
bylithium said:
I recommend philz. What rom are you flashing?
Click to expand...
Click to collapse
Was trying unified CM M8 still.
mustafu said:
Was trying unified CM M8 still.
Click to expand...
Click to collapse
How did philz go for you? I'm running sokp ?
bylithium said:
How did philz go for you? I'm running sokp ?
Click to expand...
Click to collapse
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
mustafu said:
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
Click to expand...
Click to collapse
Damn, I've messaged you.
So after a little this and that, I've realized that the md5 of the ROM isn't matching anymore, and no matter what browser and how many times I download the ROM, the md5 will now never match. Using the md5 checker on PhilZ latest. The gapps match every time when I check.
I've been using my Kingston SD card to store the ROMs and gapps, will try storing them on the phone and see how it fares.
Sent from my MB886 using Tapatalk
It's working now. Flashed the ROM, phone sat at the boot logo for 20 minutes, then the cm boot animation came on and booted from there. This is the 3rd AHD I've owned but the 1st to have this very strange behavior.
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
OK guys and gals I need help with a kernel flashing problem. I want to take the kernel from a rom and use it in another rom. I'm not going to name roms just that they are compatible roms. Here's what I did. I extracted the boot.img file from a rom. Then boot in twrp and flash the img file then flashed supersu 2.79. Reboot but I always get stuck in bootloop. What am I doing wrong?
Sent from my SM-N920K using Tapatalk
crazynewfie said:
OK guys and gals I need help with a kernel flashing problem. I want to take the kernel from a rom and use it in another rom. I'm not going to name roms just that they are compatible roms. Here's what I did. I extracted the boot.img file from a rom. Then boot in twrp and flash the img file then flashed supersu 2.79. Reboot but I always get stuck in bootloop. What am I doing wrong?
Sent from my SM-N920K using Tapatalk
Click to expand...
Click to collapse
Then it would appear that the kernel is unsupported on the other rom, for example you can't take a stock kit Kat roms kernel and use it with CyanogenMod roms. However without logs, no one is going to really be able to tell you what's really wrong..