CM10 Alpha 3 Problem? - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.

Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.

Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.

mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.

Related

Boot Loop Issues

Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
daygobaker said:
Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
Click to expand...
Click to collapse
Bump? Anybody?
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398[/QUOTE]
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Clear cache clear dalvik cache flash radio if you has issues refresh Rom from scratch DO NOT REFLASH RADIO
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Nope. Just wipe dalvik and cache and flash it. But it's likely to be an exercise in folly anyway, because it you have uclf5 and you flash uclf6, you still have the uclf5 libs. Changing the radio libs is a much more complicated procedure and without doing so you get limited benefit from flashing a new radio. But sometimes it does help anyway. Might be worth a try if you're getting poor connectivity.
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
No need to do a whole clean install simply to switch out the radio. I 95% positive you only need to wipe cache, dalvik, flash radio and reboot. I only changed radio once and it was during a clean install so I never really paid that close attention to the steps when you put it over the top of your ROM. Do what I said and you should be fine.
Or grab the torch and pitchfork. Jk there's nothing to worry about
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Still bootlooping...
Mike on XDA said:
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
Click to expand...
Click to collapse
Hey Mike,
I've been bootlooping as well. A little background...
I'm on CWM Touch 6.0.1.2 _sk8erwitskil_
I was on cm-10-20120812-EXPERIMENTAL-syyrocket-alpha3
Yesterday, I went to cm-10-20120912-UNOFFICIAL-skyrocket
I was ok until just a little bit ago I was on a call and the phone rebooted. Since then, bootloop-city.
I tried this procedure, reflashed 0912 and no joy. I think, at this point, the unreliability of CM10 (at this time) has worn thin (no dis to all the awesome developers out there) and I just want to go back to a stable CM9.
Any suggestions?
Thanks,
Bob
EDIT: Ya know, just when you think all is lost, there is Nandroid! I'm back to CM9 and no longer bootlooping!

[Q] Stuck on bootscreen after flashing [JB]Unoffical MIUI 2.9.14 Skyrocket[PORT]

Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
shentheory said:
Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
Click to expand...
Click to collapse
Couple things.... did u format data/system? Also what recovery are u using?
Deliberate said:
Couple things.... did u format data/system? Also what recovery are u using?
Click to expand...
Click to collapse
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
shentheory said:
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
Click to expand...
Click to collapse
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Deliberate said:
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Click to expand...
Click to collapse
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
shentheory said:
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
Click to expand...
Click to collapse
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Can you boot into recovery or not? If you can, just flash the rom. If you can't, yank the battery, replace it. Then, hold down both volume buttons, the press the power button, release all the buttons, you should be able to get into recovery.
Deliberate said:
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Click to expand...
Click to collapse
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
You'll have to use odin, and reroot your phone.
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
shentheory said:
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
Click to expand...
Click to collapse
I had the same problem, but while my phone was stuck on the MIUI boot screen i pulled the batter, got into recovery again and simply did a factory data reset just once and then it booted up, but my issue is that i get no data at all no mater what version of MIUI I try to flash.
mimart7 said:
You'll have to use odin, and reroot your phone.
Click to expand...
Click to collapse
Even if my stock rom is already rooted? I'm not against trying it, I'm just curious to how that could affect it. Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
I will do this and update when I do, Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
Ya I agree try downloading it again. Check the md5 and flash that ROM again. If it doesn't work your gonna have to Odin!
There were a lot of complaints of boot loops when flashing, so I pulled the DL link. I actually stopped using miui and moved back to CM or AOKP, depending on which one is most stable at the moment. Every once in a while I give miui a try, but I never stick with it. If you want miui, I suggest you follow Lithium's thread. His version is the officially supported miui rom.
I can confirm heres what i did to fix i had the boot loop.. all i did was run DARKSIDE Superwipe x2 Times. Then i installed MIUI Rom. Then i Factory Reset. Try booting wait a little bit. If still not going threw remove battery and boot to recovery and factory reset one more time then reboot. So once again.
1. DARKSIDE SUPERWIPE x2++ 2. Install MIUI Rom. 3. Factory Reset. 4. Boot. 5. (If still looping) Remove battery Then recovery. and Factory Reset and boot again. Your welcome
Can we move this to q and a?
Sent from my XT894 using Tapatalk 2

[Q] Having slight problems with CROMI 3.0.4

First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?
sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do

[Q] Samsung Galaxy SIII d2spr

Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!
JacobGates said:
Hey guys, I am having trouble flashing some roms on my Sprint Galaxy SIII. Some of the unflashable roms include: Carbon 1.6, Pac-Man, and a few other's I can't remember the name of at the moment. Successful flashes so far are Slim, Cyanogenmod 10, and Carbon 1.5 (but with some minor issues). I googled this and the only things that came up where possible bad downloads but I have downloaded these bad ones over and over and have no different outcome. Okay so what happens when I try to flash these is it will say successful in clockwork recovery, then when I reboot the device it get's frozen in boot. On Carbon it just was black but the power button wouldn't respond until I pulled the battery out and put it back in so I assume it was in boot. Pac-Man shows the blue android Galaxy SIII screen and just stays there. I read somewhere to leave the phone for 15 minutes after a flash so I have tried that with both of these and nothing changes. The successful flashes don't take more that a minute or two. So I have no idea what is going on and now I am begging to think it might have something to do with my rooting method choice. Any suggestions or words of wisdom for me? Thank you!!!
Also so rule out some questions ahead of time: Yes I wipe system/factory reset, yes I wiped cache, yes I wiped Dalvik cache, I flashed them from my external sd card (sdcard1), I used the motochopper method of rooting from here: http://forum.xda-developers.com/showthread.php?t=2286241 , I had no problems with the motochopper root process according to the instructions. Okay I think that is all the standard questions, please ask if I missed one. Thank you again!
Click to expand...
Click to collapse
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.
mcgrabowski said:
It's a good practice to wipe cache and dalvik AFTER flashing the ROM. Also, sometimes I'll have better luck flashing a particular ROM with TWRP if it doesn't flash well with CWM, and vice versa.
Click to expand...
Click to collapse
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.
JacobGates said:
Oh, I haven't heard about wiping cache and dalvik after before, I will try that with one of them and see what happens. I did try TWRP once but it wouldn't do much of anything; I couldn't get it to mount the sd card, nandroid back up, and a few other things that I don't remember at the moment but maybe I had a bad download or install with that. Any suggestions on where to get it? I did it through goomanager last time.
Click to expand...
Click to collapse
Nandroid backups are NOT compatible between TWRP and CWM, so that can always be tricky trying to switch between the two and still being able to restore if needed. As long as you don't delete the folder where your backup is stored on the SDCard, you should be able to flash back to your other recovery and restore if it doesn't work out.
I've flashed recoveries through GooManager, Rom Toolbox Pro and Rom Manager as well as downloading the recoveries directly from their website and flashed them manually. (CWM or TWRP)

Having problems going to CM12

I'm having a problem when I flash the CM12 ROM.
While having CM11.x I go to Settings and navigate to "CM Updates" where I can see a list of Nightlys and stable CM releases. When I install the new CM update this way everything seems to go okay, however This may be normal, I get a message from CWM "Possible Root loss, fix?",.. I select yes and it boots up, runs through the whole "Android is upgrading" message and all. When the phone is finally ready for use I get spammed with millions of messages saying "Application has stopped" and they will pop up infinity in less then a second. I have to hold power and tell the phone to reboot into recovery so I can resotre from backup.
I also downloaded the ROM from CM website and flashed it using "ROM manager". I get the exact same issues sadly.
What could be the problem?
Is CWM not compatible with lollipop?
Do I need to run a factory reset and wipe my phone before flashing?
I've been fiddling with this all day now. -Sigh-
EDIT:
Should I flash the latest version of "gapps" ?
You're going to need to do some reading. Installing LP over KK thru a nightly isn't going to work. You'll need LP Gapps for starters and you'll need to go into recovery and do some wiping before you flash. There are some good LP roms here: http://forum.xda-developers.com/lg-g2/development with full installation procedures. Also, most are using TWRP for recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 You may also need to flash a different baseband but you'll find everything you need in the general development section. Also, next time you really should post your questions in the Q&A section. Anyway, do some reading and you'll be good to go! :good:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Traceguy said:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Click to expand...
Click to collapse
First let me apologise, I see that you are in Q&A and I'm the one that doesn't know which forum he's in.
Next, well I've used both CWM and TWRP. Personally I prefer TWRP but as long as you're on the latest and greatest you should have no problems from what I've read. And if you do just flash over to the other and see if it fixes the problem. I've been using the 10D radio for quite some time now and it works for me.
As I go from rom to rom I always do a clean flash, wiping data, system, dalvik and cache. I rarely do a dirty flash but that's just me. As long as you can recover from the occasional boot loop you'll be good. :laugh:

Categories

Resources