Related
I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
kromosto said:
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
Click to expand...
Click to collapse
Flashing the PhilZ kernel via Stock Recovery wouldn't work? That seems to be the most simple method. Does HydraCore have advantages over PhilZ?
it should work too. i just write the method i used and of course it is not the only method to do it.
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Great, thanks.
dr.ketan said:
yes you can root directly from stock recovery with Phillz kernel (Method 1A) OR with simlpe SuperSU file (method 1B)
read this
http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
I found another recent thread. This was also helpful, thank you!
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
orificium said:
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
Click to expand...
Click to collapse
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
orificium said:
I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
Click to expand...
Click to collapse
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
koosh34 said:
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
Click to expand...
Click to collapse
The Kernel version looks the same to me as it did before I went to PhilZ. I rebooted into recover to make sure CWM is on there, which it is. And I installed a custom boot animation to make sure that worked, and it did.
Sounds like I should go to HydraCore Kernel first since it's compatible with TW ICS and JB then flash ParanoidAndroid ROM.
m_rajaganesh said:
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
Click to expand...
Click to collapse
Thanks, sounds like my best course of action is to flash HydraCore now and that way I can test various ICS/JB ROMs.
Since my original post I have:
Flashed PhilZ-cwm6-XXLRK-XEU-2.7-signed kernel in stock recovery to get original root and safe kernel.
Flashed GL_HYDRACORE_v5-4_STD kernel because I thought that's what I needed for PA.
Flashed pa_n7000-2.51-24OCT2012-192916 and followed instructions from Hydracore thread which said to flash kernel after done flashing new ROM and gapps. However - PA would not boot after that. I also tried pa_n7000-2.52-29OKT2012-101254-Utacka this way. Same problem.
So I decided to flash pa_n7000-2.51-24OCT2012-192916 this time but without changing the kernel. Booted fine this time and my phone flys now! Way faster than Stock ICS 4.0.4. It's nuts that official ROMs, by comparison, are so slow.
So I'm trying to understand how to know which kernels will work with which ROMs. So I've been reading the various stickies and this thread in particular - very carefully. And I see the part about "WARNING: Do NOT use the below listed kernels for any CM10 build dated October 3rd or newer because your system will not boot.". I assume this why I was having issues after flashing Hydracore immediately after PA? And if I'm understanding this right, I could use the new HydraCore v7 with this PA JB ROM I'm on now? Is that because of this new MALI driver?
I did an EFS Backup after I did the original PhilZ kernel install but I never did a Nandroid backup while I had stock ICS. Should I just do that on any functional ROM now to make sure I have a full working copy of something to get my phone restored if something goes haywire? Is that the idea?
Also a lot of people seem to recommend flashing ROMs using PC ODIN. Is this considered safer or less risky than using CWM?
ParanoidAndroid JB imilka build has been great - but I noticed a few annoying issues:
1. WiFi signal seemed a lot better in Stock ICS than it does with PA. My signal is always "Poor" in my bedroom and I'm not very far from the wireless router but when I'm in the living room - it's excellent. Is this to be expected or is there something I can do about that?
2. Audio issues - sometimes I have to play with the volume to get speaker phone working after hitting the on-screen toggle.
3. None of the Voice Input stuff works. It just says "Initializing" and then "I didn't catch that". Also described near the end of the PA thread but haven't seen anyone reply with a fix.
4. No timer/stopwatch built into clock app. Can someone recommend a good app?
5. When I change the Slider shortcuts under Settings->Interface->Lock screen, they don't save. It always go back to default - Camera, Google Search and Unlock options only.
6. Looking for a nicer clock widget. Can someone make a recommendation?
Just wanted to point out that I love that it automatically had the StraightTalk APN configured for me. I know you're probably thinking - yeah so? - but I'm relatively new to android ROMing - just been lurking for awhile - so it was a pleasant surprised.
Any help would be greatly appreciated.
Hi guys,
I am new to this forum and to flashing custom roms in particular. I have read a lot of stuff about the eMMC chipbug and how to avoid it. I want to install pa_n7000-2.53-05NOV2012-125144-Utacka from stock ICS 4.0.4 with this kernel: speedmod-kernel-n7000-ics-k3-15-Odin. Is it safe to flash the PA with the CWM of the speedmod kernel or should I go back to gingerbread as I have read on some other fora?
Thanks in advance!
yes its safe. speedmod is a safe kernel
nokiamodeln91 said:
yes its safe. speedmod is a safe kernel
Click to expand...
Click to collapse
So all I have to do is reboot in cwm recovery, and install PA from sd card, then install Gapps, then wipe/factory reset, wipe cache and wipe Dalvik cache and it should work 'without' risk?
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
nokiamodeln91 said:
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
Click to expand...
Click to collapse
And then it should be good to go or should I wipe again?
not until you face any app issues or so
want to be safe before flashing PA
hi guys
i m using rocket rom. now i want to flash PA 2.99
i m concerned about this warning...Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!
what should i do..?
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
nokiamodeln91 said:
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
Click to expand...
Click to collapse
YES it has one of philz safe kernels..
so what i think is its totally safe to flash a new rom if u have a safe kernel. Am i right???
what if i flash a kernel(safe one) which is not compatible with my currrent rom....is it risky or my device will just not boot or anything else.....??
Hello all... After reading here and there and in other forums, I have a series of questions that I would really appreciate if anyone can answer based on facts...
I currently have a Galaxy Note N7000 with this settings:
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version:
3.0.15-n7000XXLPY-CL474507
[email protected] #3
SMP PREEMPT Fri May 4 04:49:06 KST 2012
Build Number: IML74K.XXLPY
I want to install the 4.1.2 leaked version (already downloaded it) BUT I have some questions:
1.- I have read in different sites that I just need to do it with ODIN, no wipe required; and in other sites I have read that after installing, a wipe is required. Which one is it?
2.- According to many sites, by wiping I am at risk of hard bricking my note because of the death bug found in ics kernels. Should I still wipe?
3.- If after testing 4.1.2 I decide to roll back to I.C.S.... Again I should do that via Odin... but again I should wipe right? At risk again of bricking?
4.- This leaked version DOES NOT accept the s-pen functions at all right? so basically my spen would just be useless...
5.- THe recovery that is installed in the phone is the basic recovery that came with the phone, I havent changed it... I have read that installing some recovery files is dangerous. Which recovery is recommended?
6.- My note is NOT rooted... Does this affect my possibility of updating with this leaked firmware?
7.- and final... Do you guys recommend that I update or should I wait for the official firmware?
Sorry for the long post, but I need advice from the best ...
Greetings from Venezuela
1. you can install that without wipes using PC odin. but its a matter of luck. if it gets stuck in a boot look then you will need to do a factory reset and for that to be safe you need to install a safe kernel Philz XXLSA (i guess thats what you downloaded)
get it from here
http://forum.xda-developers.com/showthread.php?t=1901191
can be flashed using stock recovery and external SD
2. No, Always install a safe kernel and perform wipe
3. You may have to wipe this time for a proper boot as it might enter a boot loop. Same procedure, install Philz and do a factory reset. Its better to do a nandroid backup of ICS rom if you wish to return back to ICS. this way all your settings apps and customizations will be restored.
4. Incorrect. Spen is fully functional on JB leaks TW based.
5. Philz works perfectly with JB TW roms. Recovery is not dangerous. Its what you perform on it without proper reading is dangerous
6. No, PC odin can successfully flash a JB TW rom on to a non rooted Phone. But if it enters a boot loop install Philz kernel to do a reset from recovery
7. Its a long wait and no one knows when its gonna come. so if me, i would do it and i have been on all the JB TW roms available till now.
I would say, do it, do it the right way and you will enjoy the phone.
You can root your current ICS phone using the Philz kernel PhilZ-cwm6-XXLPY-XEN-v2.7 and then do a backup from recovery to be able to revert back with no problems.
Thank you so much for your reply... will do it today
Bienvenidos
Dude, another question... When you say JB TW version... What do you mean by TW...? I downloaded the one from sammobile PDA N7000XXLSA CSC N7000OXALSA... Is this a good one?
Yes. TW is TouchWiz, samsung Roms
You rock! Thank you so much... I will start doing this right now... Hope it doesnt die on me... I'm going to flash the PhilZ file and then work through the JB update... Crossing fingers...
anything, just update the post
Quick question... First: flash PhilZ... Then Wipe and then Odin? or do I go with Odin and then Wipe Data/Cache
first flash Philz, boot into recovery do a backup, then Odin, install Philz for XXLSA then wipe
Ok problems!!!! Flashed Philz (link you gave me) and when reboots, it doesnt get past the NOTE logo... I entered Recovery to do a backup and gonna go wo download mode with ODIN to update to JB and then do wipe from Philz... I-m scared beyond my pants if that makes sense at all...
Your current ROM is XXLPY right ?, which kernel did you install ? If you installed an ICS kernel , your phone should boot anyway, but if you installed a JB kernel then it wont
Yeah my bad... I installed a JB PhilZ kernel... I did a backup and flashed via ODIN the leaked 4.1.2... It loaded fine... , now my question is... Should I still update to the JB kernel for my version of JB? or do I stay with the one I installed... another question... should I still wipe?
OK. Main thing first. Now that you have backed up your rom, and the backup contains a JB kernel and ICS rom, so in future if you choose to restore the backup, dont be surprised if the phone does not boot. Later change the kernel to ICS
Which kernel did you install, update to your version of the kernel.
If the phone is fine, dont do a wipe. You can do it when you face some issues like Force close of apps or something not working as it should
I get it... will update the Philz to the right vkernel... Everything is working beautifully... Thank you for your support and patience!
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!
So... been using supernexus build4 for some time now. nice rom, good work from Faryaab.
unfortunately, I need to flash it to stock firmware, warranty stuff...
any help would be apreciated. tips on safe flashing, safe kernel, wipe, etc...
I am on:
android version: 4.2.2
N7000UBLP4
[email protected] #1 wed apr 3 21:52:49 bst 2013
supernexus 2.0-n7000-build4
JDQ39
Download the stock Rom (www.sammobile.com or from Dr. Ketan's thread here in XDA) from your region and install it with PC Odin.
I see... I´ll try this tonight
And all that talk about safe kernels, bricks, etc? is it really that simple?
I have used Odin before, but wasnt aware of these dangers...
Thanks:highfive:
Supernexus has a safe kernel with the CWM recovery, the brick issues will not happen while performing wipes. But now as you are going back to ICS, do not perform any kinds of wipes on the stock ICS kernel, you may brick the device if you do so. So before you flash the stock ICS ROM, flash it after a data and cache wipe in the CWM recovery that comes with the supernexus.
Varad297 said:
Supernexus has a safe kernel with the CWM recovery, the brick issues will not happen while performing wipes. But now as you are going back to ICS, do not perform any kinds of wipes on the stock ICS kernel, you may brick the device if you do so. So before you flash the stock ICS ROM, flash it after a data and cache wipe in the CWM recovery that comes with the supernexus.
Click to expand...
Click to collapse
Nice info.
Couldn't try it yesterday. maybe i´ll have the time today. then I´ll post the outcome.
thanks.
Hello members,
this is my first post on this forum.
I have a common problem when installing custom ROM - particulary Paranoid Android.
Every time I try to flash the ROM I get the same error (the worldwide famous STATUS 7 ).
I admit that I am new to rooting/flashing phones and that I might be doing something wrong, but I can't figure out what I'm doing wrong.
I've been doing a 3-day long research on the interent and especially this forum but I couldn't find anything that would make it work.
Here is the basic info about my device:
I have a Samsung Galaxy Note GT-N7000 (international model).
My Android version is 4.1.2.
Baseband version N7000XXLT3.
Kernel version 3.0.31-1103517 [email protected] #3 SMP PREEMPT Sat Apr 20 02:25:55 KST 2013.
Built numer is JZO54K.N7000XXLT5.
Here is a short list of things I've already done in order to solve my problem:
1) My phone is rooted using SuperSU;
2) I have installed ROM Manager and downloaded the latest version (6.0.1.2) of ClockWorkmod Recovery (CWM Recovery) for Samsung Galaxy Note N7000;
I have even tried with older versions of the same Recovery but the problem wasn't solved;
3) I downloaded the Paranoid Android from links given in this forum. I've tried with several different versions of PA. For instance I've tried ParanoidAndroid 3.10, ParanoidAndroid 3.99, ParanoidAndroid 3.99 RC2 but the results were same;
4) After that I tried to download PA via goo.im and make shure that I didn't download the wrong version of PA (but that was highly unlikely because there was always a "n7000" part of the name of the ZIP file);
5) I downloaded the Gapps as well, both via goo.im and via forum links but I didn't even get to the part where I should install the Gapps;
6) I found another possible solution on this forum and that is editing the updater-script located in META-INF/com/google/android. I did it in several ways mentioned by different people in the net/forum each time starting from scratch with a fresh download and a untouched updater-scrip (just to make sure that the previous edits wouldn't effect the current edits). And should I even say that this didn't solve my problem?;
7) After I read that the issue might be in CWM Recovery I googled for another recovery and I constantly ran into the Team Win Recovery Project (TWRP) but it seems that there is no version of TWRP for Samsung Galaxy Note N7000;
Now I'm stuck with my stock rom and I would like to try out the benefits of custom ROMs.
If there is anyone who could help me out with this I would be so glad.
If you have any questions about device, software or methods I've alredy tried out (or didn't) please feel free to ask/suggest.
Thank you all in advance!
Vaskelichius
SOLUTION!!!
I would like to thank once again to nokiamodeln91 who helped me out with this issue. If this solved your problems please thank nokiamodeln91. You can find his posts below.
The problem was solved using PhilZ. Here is a link to the thread where everything you should know about PhilZ is explained:
http://forum.xda-developers.com/showthread.php?t=1901191.
I'd like to underline that you have to choose the right kernel according to your built number. In my case it is XXLT5. Just follow the link above - it is all perfectly explained in a few posts.
After that I installed ParanoidAndroid 3.99 and the matching Gapps from:
http://forum.xda-developers.com/showthread.php?t=2120803.
ParanoidAndroid is just on of many custom ROMs and it is up to you to choose the one that suits you the best. I was just giving a example of what I did.
I hope that this can help some of you and save you time and nerves! :fingers-crossed:
For note you will first need to install a custom kernel. Then you can install the ROM.
What's the kernel on your device?
nokiamodeln91 said:
For note you will first need to install a custom kernel. Then you can install the ROM.
What's the kernel on your device?
Click to expand...
Click to collapse
Hey, thanks for your time!
Isn't my kernel listed in the first post? Is this what you're asking for:
Kernel version 3.0.31-1103517 [email protected] #3 SMP PREEMPT Sat Apr 20 02:25:55 KST 2013?
If not could you tell me how to find what kernel I'm using?
Thanks in advance!
Can't really make out what the kernel is. You mentioned you are rooted. So did you flash a kernel like Philz to root?
If not then you can head over to his thread and flash a kernel corresponding to your build number. Then you will get permanent cwm recovery. Then you can flash a custom ROM.
Installing cwm from ROM manager does not stick after a reboot and could be risky.
nokiamodeln91 said:
Can't really make out what the kernel is. You mentioned you are rooted. So did you flash a kernel like Philz to root?
If not then you can head over to his thread and flash a kernel corresponding to your build number. Then you will get permanent cwm recovery. Then you can flash a custom ROM.
Installing cwm from ROM manager does not stick after a reboot and could be risky.
Click to expand...
Click to collapse
No, I didn't use Philz.
Could you please give me a link of the thread you've mentioned?
Thanks!
Its in the android original Dev section. Very active thread.
nokiamodeln91 said:
Its in the android original Dev section. Very active thread.
Click to expand...
Click to collapse
Alright. Thank you! I hope I would understand the whole process and get custom ROMs working.
Thanks again!
Rooting with philz kernel is simple. Search for the kernel matching your rom and place I on external SD. Boot into recovery and flash the kernel. Then reboot into recovery. You should have cwm. Now your are ready to flash a custom ROM. Read the flashing procedure on the ROM thread instructions.
nokiamodeln91 said:
Rooting with philz kernel is simple. Search for the kernel matching your rom and place I on external SD. Boot into recovery and flash the kernel. Then reboot into recovery. You should have cwm. Now your are ready to flash a custom ROM. Read the flashing procedure on the ROM thread instructions.
Click to expand...
Click to collapse
I found the right kernel, downloaded it and copied it to external storage. I also copied the ROM and Gapps ZIP files. I read the instructions both for Philz and ParanoidAndroid. I'll give it a try later and if everything works as supposed I'll post it and I'll change the thread title by adding SOLVED.
Everything is workin perfectly! I had no trouble installing Philz, ParanoidAndroid and Gapps.
I'll edit the first post with details.
Fix for status 7 error
Hi there
I got the same error when i tried to install custom ROM (cm11) kitkat on my Note N7000.
The Status 7 Installation aborted was fixed when i installed a suitable kernel for the ROM in this case it was raw_kernel_r5_k44.zip
Hope this helps someone
Martin
I get problem when installing rom its coming installation abborted problem plz help me i m very much tensed