Related
Is it ok to upgrade from Assonance 5.2 to Cognition 3.04 directly? or do I have to go back to stock and then upgrade?
Thanks
green
I think the recommended way is to go back to stock and flash.
It is recommended to return to stock first.
Having said that, I have flashed about 100 times, and never returned to stock first. If the ROM has a wipe, and no wipe option, just choose the WIPE version, and you should be OK.
If your NEW to flashing - I would suggest going back to stock.
I would read the instructions of the chef/developer on if you need to disable any type of lagfixes etc before attempting to flash over the top of another ROM.
And the reason for flashing back to stock as it will wipe all remnants of the prior ROM (where it matters) from your phone letting you kind of start "fresh". This prevents any type of conflicts (i.e. forgot to disable the prior lagfix) and soft bricking your phone.
So - flash away as long as you understand how to recover from a failed flash.
Do not use odin 1 click if you have a build 1010 phone. There is a longer route you have to take to get back to stock. In general, just erase all user data from clockwork if you have the red recovery and are moving to another rom with the voodoo lagfix. Save odin for brick situations or if you are having problems.
Can =/= should. Spare yourself the trouble and time later, and just spend the time now to do it right. Backup, flash stock, master clear, load new ROM. No guesses, no trouble.
thanks folks so, if I have to flash to stock, can I use the stock rom saved/backed up in clockworks when I originally flashed? or is there any other method I should follow?
thanks
One click odin has the OEM ATT ROM built into it. Bloatware and all.
Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.
before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.
The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over
So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?
I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot
I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot
I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot
I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Apologies, but since I am a new user, I was not allowed to post in the thread in developer section.
I had bought a pre owned phone, on Rocket ROM (GB based), however as S-Pen apps were not working I decided to go on the stock ICS rooted way.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=1424997
I had downloaded the stock INdian ROM
N7000XXKK3 ------ 2.3.5 2011 November------ N7000ODDKK1 ------------------------India -------------------------Download
Click to expand...
Click to collapse
I followed the steps, downloaded Odin, and put the TAR file in PDA section, and flashed. All goes fine without error, on the phone it says everything is installed successfully. However after the process the phone just keeps restarting after the Samsung logo.
Have I done anything wrong here? How do I rectify the mistake and get my phone working
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Akiainavas said:
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Click to expand...
Click to collapse
Umm, pardon my ignorance as I am migrating from an ancient Nokia device.
No, I had done no such thing, no backups too as I just had it for a few days and no data so to speak of.
Should I be doing a wipe in recovery menu? And doesn't flashing the device, formats the memory too?
I think it should, but for some reasons it does not. To get rid of boot loop, go into recovery and clear cache. Should boot properly then
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Yes you should do a wipe of cache memory and dalvik cache. That is availible from recovery menu. And no they arent allways formatted when flashing a new rom.
To go into recovery, do this.
Device off > vol-up+home+power. And now you are in recovery mode.
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Click to expand...
Click to collapse
Thanks, I had read up how much ever I could, and am pretty wary of the emmc bug. Thats the reason I am flashing to a GB based stock rom, and then the ICS stock rom.
The error I got earlier is by flashing to a Indian GB Stock ROM, should I yet clear cache memory in the recovery mode?
A little bit of googling tells me I should be flashing to a ROM with multiple files (different ones for PDA, Modem, CSC etc) hence I am also downloading the stock Europe based ROM. Now the query is would the stock Europe GB ROM, cause any issues to a Note bought in India?
Edit: I wiped the cache partition in recovery mode, but the bootloop persists. I will try flashing to the Europe GB ROM and update.
Thanks, folks was able to install the Europe stock GB ROM, which I later flashed to an Indian stock ICS ROM. I have rooted the phone by a very helpful guide by Dr Ketan, however I miss some of the functions available to me on the rocket GB based ROM. Especially an option to have a data on/off option in quick notifications.
What is the purpose of rooting the stock ROM? Can I delete the bloatware that comes pre-installed on the stock ROM, once the phone is rooted? If yes how?
Any safe custom ICS ROM's you guys recommend? If I am right the correct way right now seems to be to flash a safe GB based ROM everytime before you flash an ICS ROM? Correct?
Last but not the least, thanks to the folks who replied and guided me in the thread, XDA is a very resourceful place, if you search it thoroughly.
About notification toggles - they are available in some roms, in others - not.
As far as rooting is concerned - yes, you can delete almost all the bloatware. There is a thread with APKs that are safe to remove - check it out and feel free to delete everything you won't be using. How ? Simple file explorer with root capabilities will do. Here's the list, thanks to pulser_g2:
https://spreadsheets.google.com/spr...1gdDJRekl4QmkyNmIzUmRvX2h3UDVkQXc&output=html
Safe custom ICS ROMs - I'd say go for CM9. For me, AOSP is the only way to go with Android. If you want TouchWiz based roms, however, can't really help cause i've never used them - there are plenty in development section though.
Nope, you don't need to flash GB ROM everytime. The problem with wipe affects only stock ICS roms ( so with stock-kernel based roms from Samsung, yeah, that's recommended ). But if you're going to flash/change/update roms like CM9, Criskelo etc. there is no need to go back to GB everytime.
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
arturutrata91 said:
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
Click to expand...
Click to collapse
Download abyss from the following site:
http://downloadandroidrom.com/file/...rnel/AbyssNotekernel42CWTouchOriginalLogo.tar
Flash the file with PC odin then reboot into abyss recovery. You can then do the wipe.
If you need more information, go to this website:
http://rootgalaxynote.com/galaxy-note-root/how-to-root-galaxy-note-gt-n7000-method-2odinheimdall/
Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
can you try go back to stock GB rom.. then upgrade to ICS and root using Dr Ketans method and then install Hydracore
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
jeetu1981 said:
You flashed Hydracore on GB rom? that's the main reason behind your problem, this Kernel is not for GB. Now either flash custom GB kernel or flash stock GB firmware using pc odin and then root it. Check post # 2 in this thread for rooting. (I guess you know how to do this )
Once you have root and cwm recovery, you can flash any custom rom you want.
Click to expand...
Click to collapse
Hot damn you guys are quick!
Silly me! :silly:
If I install any GB kernal can I then install CM10?
S-pen said:
Before I begin, yes... I did search and look through a few threads with similar titles but did not find my problem.
I am not a phone geek and I am new to all this, but I rooted my Note along with a "Franco kernel", which worked successfully. My phone booted up as it was before (in fact I noticed absolutely no difference in my phone, whatsoever).
The problems begun when I tried to install an "Abyss" kernel via CWM, which apparently installed successfully, but the phone would never get past boot-up (not so successful after all, huh?). I realized that it wasn't going to work, so I though no problem, and went back into CWM and re-installed the Franco kernel that I was using before (which worked). Strangely, this kernel, too, would now no longer boot.
I successfully restored the phone with a GB rom via odin (teriible rom), and proceeded to install the so-called "Hydracore" kernel (love the names) via cwm.... this kernel made things even worse. Once again the installation was supposedly "successful", but the phone doesn't go past boot. This time, it gets stuck on a very dim black screen, which isn't actually black, it is a dark creamy/pink hue that you can only notice in absolute darkness. (WTF?) This screen has random black blotches on it, but again, if you are in a lit up room the screen looks completely black and you cannot tell that it is actually lit. When I say that this kernel made the problems even worse, I say that because when this happens (dim black screen), I cannot even enter CWM recovery at all to try and install a different kernel. From here, I can only access download mode, and have no choice but to restore the phone with the GB rom via odin. I did so, and proceeded to install the latest version of "Hydracore" (v5.4) posted right here on XDA by the member 'chasmodo.' This time, I did the installation of the kernel via odin, which, once again, was supposedly successful... and once again a lie, as the phone just goes into the same black screen, with no option other than download mode.
The sole reason I have wasted hours of my life researching and understanding mobile phone terminology in the past few days is so that I can have jellybean on my Note. It seems that I am unable to do this because the Kernels are not working on my device. I have a very powerful and capable phone, which is currently stuck on this GB rom (which I think has to be the most terrible piece of coding ever made) so any help on this would be immensely appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Alba Donzo said:
Hi there, sorry to hear of your challenges.
One thing to remember before flashing is the nature of safe / unsafe kernels. Equally as important is compatible / non compatible kernels. It's not clear from your post but did you flash Abyss on an ICS ROM? If so, Abyss is a GB kernel. It will install but the ROM wont run due to lack of compatibility.
Abyss is used by many as a Safe kernel, a base to flash a new ROM from . Alternatively, it can be used to "downgrade" to Gingerbread ROMs.
If you are intent on trying a JB ROM, I would suggest a doing a full wipe (use the numerous guides on XDA) and a kernel clean (jBroid Script Cleaner for example). Now, research Chasmodo's excellent Kernel Repository and choose a kernel. Hydracore 4.3 Standard is a good "benchmark" however you could try the Official CM10 kernel from Entropy. Reboot to Recovery and flash your JB ROM of choice.
You will now have "Full Wiped" (including Script Clean), installed a Safe (Compatible) Kernel and flashed a compatible ROM.
For what its worth, I found GB to be an excellent ROM, particularly 2.3.6 and 2.3.7. CheckROM was one of my favorite ROMs on the S2 and they didnt even feel the need (till recently) to make an ICS version.
I hope this helps. Please hit THANKS if it did.
Click to expand...
Click to collapse
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
S-pen said:
Yes, I forgot to mention that when I rooted it I was running official 4.0.3 which I got OTA. After I rooted I tried the Abyss kernel. I had read that if you try and install CM10 straight from ICS you can brick, and that you had to downgrade to GB to do this. There must have been a misunderstanding on my part as I though that installing Abyss would downgrade me to GB.
What I don't understand is that I have now installed a GB rom, yet the Abyss gb kernel still does not work.
The two members that posted mentioned that I should root, though I did mention in the OP that it is already rooted... Am I missing something?
Anyway, I want to avoid having to download any more big files. I already have the latest "nightly" build of CM10 in my SD card. Is there any GB kernel that I can install from where I am now that would make it safe to install the CM10 zip?
Click to expand...
Click to collapse
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
So the official CM10 kernel is a gb kernel? Because remember that is what I'm currently on.
And just to make sure I got you... wipe everything, install kernel (I don't understand what you mean by "go straight to rom flash"), but then not "reboot system", instead "reboot to recovery", then install CM10 rom?
Also, when you say a "full wipe" do you mean that it will erase everything like a factory reset and delete all my apps and everything else? And is there anyway to install CM10 without doing this or is that the only way?
Cm10 kernel is a jelly bean kernel, so gb rom will not run under it.
Full wipe does mean erasing everything. Coming from gb, there is no other way to install, you need a full wipe, remember, you're updating two full revisions of the os, so it's not surprising a full wipe is needed. If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Sent from my GT-N7000 using xda premium
Alba Donzo said:
If I were on a GB ROM and wanted to run CM10 I would Full Wipe (including Cache and Dalvik) then do the following -
Flash Official CM10 kernel.
Reboot to Recovery (do not go straight to ROM flash)
Once back in Recovery, flash the CM10 ROM.
Reboot device.
Click to expand...
Click to collapse
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Click to expand...
Click to collapse
How original was that....
Sent from my GT-N7000 using xda premium
SpyderTracks said:
If you're worried about your apps, root gb before upgrading and use titanium backup to backup you're apps and then restore them when on cm10.
Click to expand...
Click to collapse
Once again, my phone is already rooted... I have mentioned this several times.
chasmodo said:
If you are on rooted GB Rom and want to flash a custom JB or ICS one, this is what you do:
1. drop into recovery
2. do a full wife™ (factory reset, wipe cache and dalvik)
3. flash your JB/ICS Rom
4. reboob
Nothing else is needed, no intermediate steps like flashing another kernel in between, and especially no running Jbroid or Sybr kernel cleaning script.
Click to expand...
Click to collapse
You telling me that I can safely go straight to JB from my current GB rom and kernel?
I already have a "nightly" JB rom on my SD card, so just to be clear, all I do is go into CWM recovery, do a "full" wipe (how do I do that by the way?) and install the JB rom from zip?
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
AA1973 said:
Yes, you can go ahead. Just follow the instructions kindly provided by chasmodo.
But please, do not forget to flash GApps after you flashed the JB "nightly ROM which is on your SD Card". Otherwise you won't have Google account, play store etc yada yada.
Full wipe (aka full-wife™) means wipe data/factory reset. Nothing else.
Click to expand...
Click to collapse
Great! I am downloading the GApps for JB now. How do I install them? I understand that this is also done through CWM recovery, but how do I instal them? do I install the JB rom and reboot to recovery and then just install GApps from zip before rebooting system?
Also, does the full wipe have to be done in CWM recovery, or can I just do the normal wipe on the phone menu before entering recovery?
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
AA1973 said:
You flash the ROM by pointing the recovery to the "ROM.zip", the same is valid for "GApps.zip".
So you do the following, no reboot in recovery in between those 2 steps!
Install zip (from where it is located, internal/external SD )
*ROM.zip
*Gapps.zip
*reboot system
Wipe data/factory reset is done (most of the times) in recovery. Just get used to it. Saves you some bad habits on doing it on stock ICS ...
Click to expand...
Click to collapse
OK install ROM and then install GApps straight away, got it.
Just about the wipe, is it a simple one button wipe that wipes everything, or are there several things that I have to wipe independently? This is the part I'm not too sure about.
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
AA1973 said:
Just go into recovery and have a look. I mean, a really close look! Your topic was "need help to install a kernel" not "I don't know how to use recovery and please can someone come over to my place in order to explain me CWM recovery".
Sorry. Everything has been explained. Can't (or rather dont want to) help you further than what has been already mentioned. Period.
Click to expand...
Click to collapse
That's fine. I'll go into recovery and have a look. Thanks for the help that you did give anyway.
It worked! I have been messing around with my new Note on Jellybean and looking through all the settings. It doesn't have project butter (or at least the project wasn't very successful), but still miles ahead of Touchwiz.
Just want to extend a big thanks to everyone that has helped me out. Much appreciated.