Related
Everytime I flash I go back to stock unless its a same rom.
Ex. I was on darky 7.2 I just downloaded the rom on my phone via dolphin. Just used rom manager to get 8.0.
But can I do this for all roms? I'm kinda confused cause some say you can and some say you can't..
Sent from my phone
You do not have to. You should disable lag fix, clear cache and davlik cache, prior. Flashing back to stock is cleaner, especially if you are going from a rom with one base to one with another. You can always try without going to stock and flash stock if something goes wrong.
I never do. I just boot to recovery and flash. If I'm using a different kernel I'll reboot to recovery then check my lagfix options and then reboot.
No need to flash back to stock. If the ROM is a 'no-wipe ROM', install like you normally would through CWM/Recovery. If you have problems, or if the ROM is a 'wipe' ROM, clear cache and data in CWM and install. If you still have problems and nothing else seems to be helping, try reverting to stock and starting fresh.
Reverting to stock between ROM's is an unnecessary extra step that generally adds the risk of Odin failure/incompatibility (which can result in a soft-bricked or hard-bricked phone).
Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.
Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked
Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.
OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.
Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?
If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore
That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.
This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug
Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0
Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug
I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0
Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing
Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0
hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu
Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0
yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..
changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0
ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(
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.
Haven't bothered flashing a ROM since Cognition 4.3, which I've been extremely satisfied with.
Now, there's GB, ICS, JB, etc...
I'm probably headed to an ICS ROM, and I wanted to know what the pain is going to be like.
Obviously I'll be pulling a full back-up of the phone to my PC, but I want to lose as little as possible, so I guess my plan is as follows:
1. Filesystem backup via USB.
2. TiBu back-up of apps + generate update.zip
3. Nandroid back-up
4. ????
5. Boot in (new?) recovery, run TiBu update.zip
6. Boot phone, restore with TiBu.
Please fill in the blank, here.
What do I need as far as bootloaders?
Do I have to break out Odin or are there update.zips that will flash new bootloaders from CWM?
If I decide that I hate the new ROM and miss Cognition, am I going to be able to run Froyo again on the same bootloader or is it going to be a serious pain in the ass to get back to where I was?
I'm familiar with the (Froyo) procedures for flashing ROMs, kernels, modems, GPS firmware, etc. I jumped ROMs weekly for the first two months or so after I bought my Cappy (Dec 2010). I'm not a total n00b, but this seems slightly more involved than just Eclair -> Froyo flashing.
With the new bootloader, is the Captivate still indestructible? (apart from using a hammer, of course)
Thanks in advance to anyone with good answers.
delugeofspam said:
Haven't bothered flashing a ROM since Cognition 4.3, which I've been extremely satisfied with.
Now, there's GB, ICS, JB, etc...
I'm probably headed to an ICS ROM, and I wanted to know what the pain is going to be like.
Obviously I'll be pulling a full back-up of the phone to my PC, but I want to lose as little as possible, so I guess my plan is as follows:
1. Filesystem backup via USB.
2. TiBu back-up of apps + generate update.zip
3. Nandroid back-up
4. ????
5. Boot in (new?) recovery, run TiBu update.zip
6. Boot phone, restore with TiBu.
Please fill in the blank, here.
What do I need as far as bootloaders?
Do I have to break out Odin or are there update.zips that will flash new bootloaders from CWM?
If I decide that I hate the new ROM and miss Cognition, am I going to be able to run Froyo again on the same bootloader or is it going to be a serious pain in the ass to get back to where I was?
I'm familiar with the (Froyo) procedures for flashing ROMs, kernels, modems, GPS firmware, etc. I jumped ROMs weekly for the first two months or so after I bought my Cappy (Dec 2010). I'm not a total n00b, but this seems slightly more involved than just Eclair -> Froyo flashing.
With the new bootloader, is the Captivate still indestructible? (apart from using a hammer, of course)
Thanks in advance to anyone with good answers.
Click to expand...
Click to collapse
If you want to flash ICS or any newer rom, you should probably get Gingerbread via Kies, root, and install CWM. Many ROMs run on Gingerbread bootloaders, and many who didn't run GB beforehand, had display problems. After that, you can flash any rom you want
I just went through this and wrote up my experience here.
http://forum.xda-developers.com/showthread.php?t=1800169
bottom line is that Slim Bean worked the best for me.
As for installation, this is a pretty good guide.
http://forum.xda-developers.com/show....php?t=1350266
I recently did this with Slim Bean from gingerbread stock.
1. Use Odin or Heimdall to install Speedmodem kernel. (The only difference between Gingerbread and Froyo is whether you flash the bootloaders too.)
2. When the phone reboots in recovery, go to mount > usb. Make a back up of the internal drive and copy Slim ICS to the internal drive and flash it
3. ** Warning ** step 2 will install an updated CWM and completely format the internal drive, so make sure you make the back up.
4. Because it wipes the internal drive, it'll go into a boot loop, so remove the battery and boot back to recovery.
5. Repeat step 2 but also copy and flash the slimcommon zip.
6. Reboot and make sure it works.
7. Repeat step 5 but using Slim Bean and Bean Common zips.
8. reboot and done
When I did this, under Slim ICS the IMEI was wrong and it wouldn't make phone calls and but under Slim Bean, it all worked fine.
One issue with Slim Bean is that some apps don't show up in the Market, however, I was able to restore them with TiBu just fine.
Alternatively you can go straight from stock to CM10. It's actually simpler because it doesn't format your internal drive. You just flash it, reboot to recovery, and flash again. CM10 wouldn't work right on my phone though. (See first link for details.)
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.