I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
As long as you follow the instructions, it doesn't matter what you're coming from. See full instructions here http://forum.xda-developers.com/showthread.php?t=1419102
Notice that for the CWM method, the third instruction is to flash a particular CWM recovery to avoid potential problems. There are instructions on how to flash on the link to it.
n125 said:
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
Click to expand...
Click to collapse
Easy enough upgrade path
If you are worried about doing this, flash the ODIN "resurrector" CM9 package - it should sort out wiping and everything else for you.
If you want to do it via zip, put the zip file on the SD, do a nandroid backup, wipe data and cache, then flash the zip and latest ICS gapps.
I don't think you'll have any issues with installing CM9 using that CWM. If you do, ODIN flash latest Siyah Kernel. Go to recovery and flash CM from there and you'll be fine
Thanks for the help guys. I went with the CM9 Odin Resurrection method and then updated to the latest nightly (20120511) with CWM.
I'm very impressed with what I see so far. I'll have to keep an eye on it, but I am a little worried about the battery life. (Though considering that I am on a nightly build, less than optimal battery life might be expected..)
Also, my signal strength seems to be fluctuating a bit, usually between 3 and 4 bars, although sometimes it will go down to 2 bars. The modem that came with this build is XXLPQ. Is there a better modem that I can try, or is it just a matter of going through all of them? I was on MUGKG2 previously and it was quite stable for me.
I think LPQ must be your earlier Modem which is retained after instlling CM9, if I am not wrong CM9 doesnt contain a modem.
try KE7 modem, I have got a very nice experience with KE7 on ICS roms
Related
Hi, everyone. I'm used to rooting/ROMing/etc. on the Samsung Epic, but I'm very new to the Thunderbolt. I rooted my girlfriend's phone and had some problems with the data connection being inactive following a kernel install. I went back to as close to stock as I could in order to get everything working again, but new problems have surfaced:
1. GTalk crashes
2. Camera fails to open
3. Documents fail to open, as in Word
4. Phone fails to update, though it indicates an update is ready
Right now, she's on a pretty much stock Froyo ROM and what I believe is the stock kernel, or something very close.
I've read a bit about the camera and gtalk problems. I saw a link to a CWM flashable zip that apparently fixes the date problem that causes the closes. However, it wasn't clear if that zip was only for GB for if it also works for Froyo. Please advise on that.
I haven't seen any reference to the document opening problem, unfortunately.
As far as the update thing goes, I'd rather keep her on a custom ROM, as I assume the update will kill her root.
Basically, I'm looking for a stable and reliable kernel, ROM (preferably GB), and radio combination that is known to run without issues. Last time I tried to pick a combo myself, it ended up killing the data connectivity, so I'm trying to figure out the "best" combination that is known to work. Also, if there are any Thunderbolt-specific flashing procedures that tend to cut down on force closes and errors following a flash, please let me know.
Thanks a lot,
-Rob
When you say update, you mean OTA? If so, you have to be 100% stock to get an OTA to install. You can't have a custom recovery installed.
Pretty much all the GB ROMs out there are pretty stable. The question is, do you want a Sense ROM, or AOSP?
As far as kernels go, Imoseyon's kernels are top notch. I prefer jdkernel for AOSP ROMs though.
I use the latest OTA radio and have 0 problems, and it works for both froyo and GB ROMs.
...
Thanks a lot for the response. I'd like to keep on the Sense side of things, just to keep the user experience sort of like stock for the girl.
So, to go one step at a time:
First, the radio. Is this the latest OTA radio that you mentioned (MR2?): http://forum.xda-developers.com/showthread.php?t=1154010
Second, the kernel. It looks like nerozehl has a great kernel that's based off of Imoseyon's leankernel. There are so many versions, though. Would the latest Sense kernel 2.3.6 (from http://forum.xda-developers.com/showthread.php?t=1099996) be appropriate, considering the ROM below?
Last, the ROM. It looks like SynergyROM is a good place to start. I believe the latest one is found off the download link near the top of this page: http://infectedrom.com/showthread.p...IGHTLYS-2.3.4-SENSE-3.0-★-☆-★?p=4368#post4368 Any thoughts on SynergyROM?
Does that combination seem like one that should work correctly?
Also, just so I have the steps correct for installation:
1. Flash radio in hboot.
2. Wipe in CWM (cache, dalvik cache, anything else?)
3. Flash kernel in CWM.
4. Flash ROM in CWM.
5. Reboot.
Thanks again for any help. It is definitely much appreciated. Can't go around breaking the girlfriend's phone, after all...it just looks bad!
-Rob
There is an issue with the lib files for the Camera ,which is messing up Gtalk. There is a fix in several threads, something HTC did on the new base.
Here is the fix:
http://themikmik.com/showthread.php?8436-Flashable-G-talk-Camera-Fix
...
Thanks, fillyo! I assume this works for both GB and Froyo ROMs?
-Rob
If you flash the kernel before the ROM whatever kernel comes built in to the ROM will overwrite the kernel you just flashed. I would say ROM, kernel, radio.
Oh and when you wipe I would do:
1. Wipe data/factory reset
2. wipe cache
3. Advanced, wipe dalvik cache
4. Under mounts and storage select format /system
Sent from my HTC Thunderbolt
JBO, thanks for the advice. That makes a lot of sense. Do you have any comments on the radio, rom, kernels I've selected above? Particularly the radio. I was told the latest OTA radio works well, but is that the one also knows as MR2?
Thanks,
-Rob
Sent from my SPH-D700 using XDA App
Yes the MR2 radio will work with that ROM as well as any leaked radio that is newer than the MR2. What radio works best is kinda subjective and seems to vary from person to person. I don't know if the kernel you linked is compatible you would need to ask in the Synergy thread. Honestly as far as the kernel goes I would just use the one built into synergy. I hear its quite good and has a great set of features.
Sent from my HTC Thunderbolt
I've used SynergyROM and it is an awesome ROM. It comes with Ziggy's kernel, which is an awesome kernel. The OTA Radio basebands are 1.39.00.0627r, 0.01.69.0625r
I hope you find a ROM/kernel/radio combo that works for you!
That's exactly the info I needed. I'll just stick with the built-in kernel and the MR2 radio. Thanks for all the help, guys.
-Rob
Sent from my SPH-D700 using XDA App
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I am currently running the CM9 4/8/12 nightly. It was the first ROM that I have installed so far since getting my TP less than a week ago. I wanted to try the 4/12 nightly and just had a quick question before I do so.
I am using cell phone ROM flashing logic here, so please correct me if I'm wrong. Do I just need to download the latest CM9 nightly zip, put it on the root of my TP and just flash the zip through CWM? Of course I would clear cache and dalvik first. That's how I would do it with my phone but I just want to make sure that it's the same with the TP before I bork something.
Thanks!
I went from CM9 to AOKP. It was my first ROM switch. All I did was clear cache/dalvik and did a factory reset. I wanted to do a factory reset just to be safe. I dont know how it acts yet when you just clear cache. But the way I did it worked just fine.
WizeGuyDezignz said:
I am currently running the CM9 4/8/12 nightly. It was the first ROM that I have installed so far since getting my TP less than a week ago. I wanted to try the 4/12 nightly and just had a quick question before I do so.
I am using cell phone ROM flashing logic here, so please correct me if I'm wrong. Do I just need to download the latest CM9 nightly zip, put it on the root of my TP and just flash the zip through CWM? Of course I would clear cache and dalvik first. That's how I would do it with my phone but I just want to make sure that it's the same with the TP before I bork something.
Thanks!
Click to expand...
Click to collapse
You are right... just download the latest nightly zip to your internal sdcard and flash away... wiping Cache and Dalvik in the process... nothing really different here as compared to the methods you used on your phones.
Thanks fellas!
[Q] What kind of "loop" do i have? Happens with AOKP devil and glitch ICS and CM10
First I know the phone is not bricked. I can and have repeatedly ODINed to stock EH03, remembering to atlas and repartition as per droidstyle's guide. The problems begin when I go through the rest of the guide section 4, to get and ICS AOKP rom running. (This is staging for my question to be complete. Question at bottom.)
For whatever reason the phone was stuck to only boot into (red) recovery. I had the AOKP rom MS6-devil before and I think flashed another different devil kernel over that. The phone has been completely stable for months now. I tried data wipe/reset and wipe cache, and dalvik too. It still only rebooted to red recovery (sorry don't recall the exact version). This is when i decided to ODIN and start fresh.
Maybe some side questions. Is it ok to flash different devil kernels on the devil kernel rom? I assume yes but I just needed to run through my check list. When I ODINed back to stock did that automatically restore the phone to a stock kernel as well?
So the phone ODINs fine every time and ODINing cmw4 for CW7 and GB bootloaders too. (BTW when i flashed ICS rom several month back i dont think the guild had anything about ODINing bootloaders. Is this new?). 3 finger works and I'm in blue recovery 4, i wipe data and dalvik (I've done this more than 5 times some i also tried a cache wipe with same results).
What kind of boot loop is this?
I flash the ICS rom zip that i want and it starts but the status bar on the phone make a small amount of progress then goes black, reboots to the flash the Samsung logo then goes to some splash screen that shows Icy Glitch Kernel V14 if i try the AOKP M6 official, or a splash screen of Devil Kernel if i flash AOKP M6-devil or even with CM10 i see the splash screen of cyanogenmod. If i let the phone sit on the screens for a long while all i see is a continual booting to these splash screens.
I have mucked something up with the kernel and i thought ODIN would reset that each time. If I can know what kind of boot loop i face i can go to find the right threads or make a post in the right place to get this resolved.
Actually it's normal for that to happen, after you start the install it should reboot the phone to an updated recovery and continue the installation from there. At least that's what it did for me when coming from stock. How long did you wait? Are you getting any errors? If you're still using the stock sd card that could be your problem right there. Also, I highly recommend trying a JB rom, ICS is pretty stale at this point. AOKP just released JB Milestone 1
Good tips. I didn't know that's what it should look like. I was flashing for many hours and waited 20-30 minutes. The only happenings on screen were the splash screens flashing occasionally as if the phone were looping. Im guessing now that's normal in the flashing process. I've flashed the same roms before months ago and probably the process on screen I just forgot. Ill try again later when I have time and try some jb action and report back.
When going from stock to ics are you first flashing ths build 2? There are many versions of devil available some are built for ics and aome for jb only. It's important to know which one you are dashing cause the jb devil kernels have a specific partition layout needed to get jb to run on the fascinate. I could be wrong but anything higher than 1.5.xx is jb specific.
The devil rode a unicorn named jelly bean
forsakenone said:
When going from stock to ics are you first flashing ths build 2?
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
You know I think that is it. I just blanked on doing that. I have build 1 and 2, b/c sometimes one works and one doesn't. I think I used 1 this time, but the first time I flashed ics i used build 2. Any way thanks. I am checkin out jb now too. cm10 is working great.
You didn't miss the step (to flash Build2 between EH03 & AOKP/CM10), the step was missing (temporarily) from the guide because some have found it to be unnecessary. I had the same bootloop as you when I didn't go through Build2 on the way to AOKP. Seems like the phone attempts to boot normally rather than into recovery to finish the installation of AOKP/CM10, and can't because it is midway through the installation. So did you state you had the problem when flashing CM10 as well? That's interesting, since some can skip going through Build2 and some can't. I thought maybe AOKP required it and CM10 did not... still trying to figure out what is different between phones that require it and those that don't.
Yeah I had it happen on cm10 too. I tried again but only flashed cm10 and no strange looping like I described. But I didn't flash any build before cm10.