Hello XDA Dev. I, Azeem, come to you guys with a problem and I need you all's help on solving it. Here's the story.
I was previously on Cyanogenmod 10.1.3 Stable for my phone and decided to try out the new 9-28 nightly of CM 10.2. However, when installing the rom, I rebooted in to recovery after installing it, gapps 4.3, and ajk 4.9 AOSP, but it got stuck at the Samsung logo and I could not enter recovery mode anymore nor could I boot to the homescreen. Knowing using odin to go back to stock would fix the issue, I did just that, and booted to the homescreen. Btw, I odined back to ICS 4.0.4 since I couldn't find an Odin-able tar file for Jellybean UCMD8 (if you know of any, please tell and link it to me). Anyway, I went and installed Mobile Odin to my phone and the N.E.A.K kernel ( http://forum.xda-developers.com/showthread.php?t=1614150 ) for the ICS stock ROM, booted into recovery, wiped data, cache, and dalvik cacke, installed Cyanogenmod 10.2 nightly, gapps 4.2, went to advanced, and clicked reboot into recovery.
Next thing I knew, guess what? It was back to being stuck on the damn samsung logo and I couldn't boot into recovery, yet again! I went and though why not give it another try, so I redid all the procedures I had done prior, but this time flashed the 10.1.3 stable, AND IT HAPPENED AGAIN! I was like wtf! That leads me to the question. Is there anything I can do to prevent this from happening again? I really like cyanogenmod and would love to go back, but I don't want to repeat all of this a 4th time. Thanks for your help in advance!
EDIT: Nevermind. I got UCMD8 Cooked to work, but I am scared to flash 10.1.3/10.2 because I don't want to have to deal with doing all that I did in OP again. However, I really want CM 10.1.3/10.2 back. A dilema.
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
creepyncrawly said:
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
Click to expand...
Click to collapse
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
azeem40 said:
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
Click to expand...
Click to collapse
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
votinh said:
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
Click to expand...
Click to collapse
I fixed the issue by doing the OP things and just restoring nandroid backup.
Related
EDIT: First I tried installing Codename Android as my first rom from stock rooted gingerbread. OK, I ended up having some problems where I couldn't detect the SD card on my computer, and Android was giving me no option to go into mass storage mode. I had to take the advice on ics.samsung-update.com about the MTP issue going into Terminal Emulator to get it working again.
Now that I got it working I was just going to try to flash teamhacksung's build 5 here: hxxp://rootzwiki.com/topic/11850-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-5-0114/ Read my latest post for my problem.
I'd highly recommend AOKP or THS (find at rootzwiki) ICS roms. Droidstyle's guide in the general section has everything to get you up and running. Sounds like you might've flashed the wrong recovery in odin?
Probably something like that? I dunno, either way, I got a ClockwordMod v4 flashed on there. I then installed the Codenamed Android ROM I had on the sd card and that was appeared to work just fine. It seems strange that the contacts app on this rom seems to only want to let me import contacts from an Exchange account? Kind of strange I can't seem to get my Google contacts on here. I guess I'll try to flash the teamhacksung rom.
It sounds like you forgot to flash gapps. Flash the rom you want to use, then gapps, (then kernel if you want), and reboot.
Aokp m4 ftw! Glitch kernel if you're looking for performance tweaks. Go to Droidstyle's guide in general forum for all your needs.
Sent from my SCH-I500 using xda premium
cant install gapps
I am now trying to install teamhacksungs build. This seemed to go ok, except for I keep getting errors that it can't mount the cache. Also when I try to data wipe it gives me those errors and it seems to skip some of the formats. After I flashed teamhacksung's build 5 I keep getting errors that android.process.media has stopped. Also after the rom begins running I shut back down to flash gapps and this seems to install as well, but when I boot up I see no sign of them. Anyone have any ideas?
It sounds like you may have 3-fingered into recovery after flashing ICS. After you odin the recovery, you 3-finger into it *initially*, but never again after that. Use the reboot menu.
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
Hi i am very new to the concept of rooting and flashing ROMs.
My phone is a SGH-I777 unlocked running stock 2.3.4
I have tried rooting my phone using CWM 5.0.2.3 for i777 and then user superuser 2.3.3 to root which went fine.
Now i wanted to install a custom ROM so i went ahead and downloaded the CM 9 stable for my i777 and the gapps signed package saved them both to the internal memory went into recovery mode and followed instructions as per CM wiki to wipe cache wipe factory reset and then installed the CM 9 Stable and then the gapps package. When the phone rebooted CM9 was installed but unfortunaltely no gapps and i was not gettinng any network on my phone.I tried reflashing but no good hence went back to stock and everything seemed to be working fine.
All i want to know is did i follow the right procedure or is there something else which had to be done or needs to be done while flashing any new ROM. Also if anyone can suggest a good stable ROM for the i777 i personally i like CM 9,CM 10,AOKP SHOSTOCK & MYSTIC GLORY.
If anyone can be kind enough to help me on how to install the above mentioned ROMs if its a first time for someone.
Thanks
You can try rebooting again after initial boot. Sometimes that will clear up data/network issues. Also you can go into settings-->more--->mobile networks and check your APN settings. When there you can hit menu button, then restore default apn, and reboot.
Also you mentioned your phone is unlocked. Are you using it on another carrier other than ATT? If so, make sure your APN are correct for your carrier.
Your basic procedure is fine, theoretically, it should work.
Why gapp didn't work? I don't know, I haven't run CM ROMs.
Try reflash gapp? Try reboot?
Did u download the correct gapps? I've had it happen that my big old fingers hit the wrong gapps package for the base I was running (cm9 (ics), cm10 (jelly bean) or gingerbread. Everything u did sounds right in theory, make sure not to use rom manager.
Sent from Team Pirate Headquarters. AKA yer moms basement.
I've had it happen that I needed to reboot into recovery and flash just the gapps again. Try that. Don't try to reinstall cm and gapps. Just do the gapps again.
Sent from my SGH-I777 using xda premium
It has been a long time but I do remember when CM9 first came out for our phone I would flash the cm zip and let it try to boot. Then after a few minutes I would hold down the volume +/- and power until I was back in recovery and flash cm a second time BUT this time then flash gapps BEFORE rebooting. On occasion I have still done that out of old habits when I am switching between different ROMs. Good luck
Sent from My SGH-I777 Running Red Reaper Rom
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
I have a Galaxy S2 i9100. I was wondering if it's a known bug that sometimes the screen never turns off unless I press the power button? No matter what I set Display -> Sleep to, the screen often never turns itself off. I can't see any pattern to it for when it works and when it doesn't. Is there any known apps that can mess with it, like NoLED?
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
marjune23 said:
Am on NeatRom v2.4.1, no such issue here.
Try wipe cache and dalvik from recovery, then report back please...
Another question, are you looking at your phone and waiting for it to turn off?...
If yes, Smart stay causes it to stay awake...
Disable it from Settings>Display>Smart Stay...
Click to expand...
Click to collapse
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
djondjoe said:
Apparently my phone isn't too smart, for this is no such option under Display. What does that mean?
Well right now, and since I wrote this thread it's been behaving like a dream and I can't make it not work. Yesterday, for the life of me, the screen wouldn't go out.
Click to expand...
Click to collapse
Oh forgive me, I was thinking of v5.6 hahaha...
Please disregard the Smart Stay, that is not present on NeatRom AOSP v2,4.1...
Just do my first advice, wipe cache and dalvik from recovery mode...Then Reboot...
1. Reboot to recovery...
2. Wipe cache partition...
3. Advance>Wipe Dalvik...
4. Reboot your phone...
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
djondjoe said:
Alas it still often doesn't turn off the screen after wiping the caches. Tried as low as a 15 second sleep but no dice.
Click to expand...
Click to collapse
Oh thats bad...would you consider reinstalling the Rom without full wipe or full wipe again?...
I guess it will solve now the issue....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
For now I'll try to live with it. I can confirm that a reboot fixes the problem for some time.
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
djondjoe said:
I still can't find any pattern to it. I tried shutting down all active programs, but when it's in no-turn-off-screen mode there's nothing to do but reboot. This has happened every day so far.
Click to expand...
Click to collapse
Sorry to here that mate...
It looks like you need to do a full wipe now...
Optional, do a nandroid back up...
1. Flash compatible KK cwm...
2. Wipe data...
3. Wipe cache...
4. Wipe advanced>dalvik...
5. Format cache, system, data and preload from mount and storage...
6. Flash Rom and Gapps.
7. Reboot and enjoy...
8. Report back please...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.4.1
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
djondjoe said:
I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version? I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
Maybe there's something I don't quite understand, if so please educate me
Click to expand...
Click to collapse
Before we start the lesson, let me ask you first if your issue has been resolve already?...
Don't worry I won't give up on you until I satisfied you baby hahaha...
Q. I have never actually flashed a cwm before flashing a rom (well before trying out AOSP NeatROM anyway). Why is this necessary?
A. How did you manage do flash Rom without flashing compatible KK CWM Recovery?...Unless you came from another KK Rom, it is possible...
It is necessary coz simply it is the basic requirement of KK Roms (with maliV3 drivers)
Q. Is it also necessary to find an older cwm if I want to go back to a 4.1.2 Android version?
A. Yes, as you can see in Post #3 in NeatRom AOSP thread (last paragraph)...although it is already integrated with Philz kernel...
Q. I know I had to install a Kitkat compatible cwm before flashing the AOSP NeatROM, but aren't the cwm's "backward compatibable" and can handle older versions of Android?
A. CWM are just type of recovery. Other than CWM there is what you called TWRP (touch wiz recovery program, which is used by NeatRom AOSP)). TWRP is more on just tapping on your screen to navigate your recovery.
So you need to find compatible CWM or TWRP to be able to flashback to 4.1.2. And same with Kitkat, you need to find compatible CWM or TWRP.
But there are some kernels who is now working to be able to handle to flash a KK or Jellybean. (e.g. is Dorimanx Kernel)
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
djondjoe said:
Well my phone is living a life of it's own. For the last three days the screen has worked fine except in the afternoons and evenings where the screen doesn't turn off by itself. I must say I am puzzled. I still suspect NoLED of having something to do with it all.
Yes I came from Omega ROM, and before that Cyanogenmod and others. I guess I only manually installed CWM the first time I rooted the phone. All the other times they were included in the ROM, so it's new to me I need to do it manually to revert from NeatROM. Let's say I want to try NeatRom 5.6, I can't just download the ROM and install it with Philz KitKat CWM Recovery which I already have installed? If no, what exact CWM must I use?
Click to expand...
Click to collapse
Wwaahhh read carefully mate my comment above...if you want to go back to neat 5.6, Post #3 last paragraph....
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
djondjoe said:
I read it, don't worry
Just don't get why, but I assume it's because the KitKat CWM ONLY handles KitKat ROMs and I must revert back to an older CWM recovery for older Android versions, and I also shouldn't ask all my pesky questions and just do what I'm told :laugh:
Click to expand...
Click to collapse
Nice nice...safety first ...
Hhmmnnn AFAIK there were different versions of recovery...As of now it's so hard to follow....So for me I just follow instructions (ofcorz reading comments) before proceeding....but sometimes I like being risky always hahaha...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
djondjoe said:
SO close to having 10 posts now :laugh:
If I want to upgrade to 2.5, is it really the hard way with installing the ROM all over and having to reinstall all apps? I thoughtthese custom ROMs all had an upgrade functionality in a menu somewhere.
Click to expand...
Click to collapse
If you want to retain your apps do dirty flash...but if something went wrong or you want fresh installation do the full wipe...see post below...
http://forum.xda-developers.com/showthread.php?p=49887400
Ooopppsss just a tips also, please hit thanks button if somebody help you on their comments to your post
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
djondjoe said:
Thanks!
I guess I'll be dirty then. What are the odds of success and no boot loops?
Click to expand...
Click to collapse
As you can see on my post 1% fail and 99% success...
The only main problems sometimes why bootloops occurs is users don't follow the steps provided to them...
My tapatalk Signature
Phone: Samsung Galaxy S2 i9100
Currently on Dualboot
1st Rom: NeatRom v5.6
2nd Rom: AOSP NeatRom v2.5
Kernel: Dorimanx 8.43vXX
My procedure in dualbooting
Hit thanks button if you think I helped you...