Hi XDA
I am having problems with installing CM on my P990. I have both tried the stable and the latest nightly rom, and none of them can boot.
Then I reboot after the installation has finished I first see the white lg logo, and after a few second it changes to the one with the blue line in the background.
The installation is insanely fast, like 5 seconds.
The stange thing is, that I can run MIUI without any trobles.
Anyone having some suggestions af what to do?
Does your phone seem to be stuck at the second LG logo? Remember the first boot takes much time so be patient.
Yes, stuck at second lg logo. I have waited for about 15 minuttes.
Allright, have you tried a Cm7 Kang instead? Try Temaseks Cm7 Kang.
That does not work either...
This happened to me as well. I recently got 3 of these phones (1 for my gf, 1 for my brother and one for me), rooted all 3 and started customizing.
Cyanogenmod 7.1 Stable worked on two phones (both phones got BSOD when charging) but my phone just won't boot CM7 Stable. I ended up using Temasek's KANG 204-49 and it works beautifully (with vadonka's kernel, not his latest though, haven't tried that one yet)
MIUI did work on all the phones. This is really weird but I can confirm.
Maybe you have to convert your filesystem to ext3.
Sent from my Optimus 2X using XDA Premium App
so... cm7 stable is a completely different build to cm7 nightly's from about #179 onwards. teamsek's kang's are based no the last nightly build, #204. to convert/update to the latest kang from the stable version you need to do a full backup with titanium or similar app. then... when in recovery do a full wipe, wipe cache, davik cache and battery stats. then flash your kang zip and restore your phone with titanium backup once you phone has booted up. good luck!
Related
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
oman0123 said:
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
Click to expand...
Click to collapse
You probably have the wrong bootloader and kernel...the newest cm7s are based on the 2.6.32, not the older 2.6.29 (or something), and the newest 1.2 bootloader..which you probably don't have if it's "been awhile"..lol...You have to upgrade your Cwm first, from 3.0.1.0 to 3.0.2.8, I think, then flash your Cwm to a nightly after 86??(Google to check), and it will change your boot partition to the correct one...If your nook still says "touch the future", you're on the wrong bootloader.....Also, quit using Phiremod.....it's a copy of Cm7 first of all, but by the time it's released, it's already outdated, it's not updated like it should be, and it's Douchey. Google the basics of what I described above if it sounds like that might be your problem and lmk how it works out for you....Btw....I used nightly 106 for this exact thing on another of my Nooks a few days ago and it worked flawlessly...There are newer nightlies out, but that one for sure worked.....
Sent from my NookColor using Tapatalk
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
DiDGR8 said:
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Click to expand...
Click to collapse
Ive tried all of that. hopefull mazooks way works. Otherwise im out of ideas
oman0123 said:
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
Click to expand...
Click to collapse
If I remember correctly, you can't just jump from 3.0.0.6 or 3.0.1.0 to newest...there's one in between that transitions the upgrade in bootloaders...I'm pretty sure I went 3.0.1.0 to 3.0.2.8 to flashing Cm7 nightly 106...then to upgrade to Cwm 3.2.0.1 while in Rom manager, while using Cm7....leSigh....Clockworkmod is the only thing I can't stand about using my Nook....(though I rarely need it any more) AmonRa is such a better (and fully functional) recovery build...One thing I wish we had gotten.....
Sent from my NookColor using Tapatalk
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
oman0123 said:
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
Click to expand...
Click to collapse
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
mazook98 said:
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Well Id love to try that but.....My nook wont turn on. It was fully charged today. Im either gonna make a bootable cwm or go back to stock and root again. I dont know if that will work though because its not even powering up.
Ok....i think im making progess....The newest nightly just goes into a bootloop. better than a clockwork bootloop i guess..... any advice on how to get it to install properly? i feel like im making progress. normal bootloops are better than what i was getting
Bueller............Bueller lmao.
Seriously though.....if anybody can figure this out it would make my year
Try this, install stock 1.2....
boot it up, go through the annoying setup, log into google apps, then power down.
Boot into CWR SD, this should have the os that you want already on it, and the google apps file.
THen click install from zip, choose zip, install the OS, after complete install google apps, then restart without sd
Do not format anything, it should do the trick.
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
mbarnwell said:
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
Click to expand...
Click to collapse
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
+1. I would go into recovery (I use CWM) and format system, cache, data, boot and then flash whatever rom you are trying to flash. Also, give it some time to boot up. Some roms can take a while. You can try the flashover too as Dastin suggested.
Are you using any tweaks like firerat's? There can be issues with that if your system partition is too small
Good luck!
That is a good idea
Keep rolling back versions of the ROM I want to try until something sticks.
Update the 'new' ROM to the latest version.
In the meantime, I've updated to CWM 4.0.1.5 and wiped everything possible at least twice. Plus a format all script. I will let you know if this does it for me
I still have not been able to flash any other roms, the only thing I can do is change recoveries and do nandroid restores. I am using the latest herodeck rom which is based on the CM roms. Hopefully someone will be able to help us.
And sorry about making a new post I was thinking that we were using different roms but I guess that they are actually pretty close to being the same.
A friend of mine gave me his LG Optimus 2x phone to installed AOKP M5 based on ICS 4.0.4. Currently his phone is running on ANdroid 2.2.2. I rooted this phone with SuperOneclick program successfully. AFter this I installed ROM Manager but when I tried to flash it with clockwork recovery through ROM Manager, it failed and after boot, it went in infinite boot loop. I managed to break the boot loop by pressing power and lower volume button together. Now I am stuck and don't know to proceed further.
I have Samsung Galaxy Nexus and Moto Xoom and it was lot easier to install custom ROM.
I will appreciate your help with some instructions.
Hi. Try to do wipes; cache partition, factory; davlick (advanced) and reflash again the said ROM. What CWM version you have? I would suggest 5.0.2.8, I have no problems on it. I flashed several roms, CM7 and CM9.
Hope it helps.
If I understood you don't have cwm installed correctly.
Try this: http://forum.xda-developers.com/showthread.php?p=18939518
Nvflash never fails.
And I'm not sure aokp works good on our phone, due to hard hacks necessary to run ics with outdated kernel sources concerning CPU and GPU chipset.
In case you can try Owain's unofficial builds not so far from aokp.
Striatum_bdr said:
If I understood you don't have cwm installed correctly.
Try this: http://forum.xda-developers.com/showthread.php?p=18939518
Nvflash never fails.
And I'm not sure aokp works good on our phone, due to hard hacks necessary to run ics with outdated kernel sources concerning CPU and GPU chipset.
In case you can try Owain's unofficial builds not so far from aokp.
Click to expand...
Click to collapse
Thanks a lot. NVFlash resolved the issue.
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Antonnzr said:
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Click to expand...
Click to collapse
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
DFornazari said:
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
Click to expand...
Click to collapse
I have used nightly builds of CM10 from October 15 onwards with a problen
only on the 19th release when I couldn't install anything due to an issue with
the version of Clockworkmod Recovery. Once I found out how to downgrade
that version, it's all fine (touch wood).
Sam
@Antonnzr
Rather just use normal GAPPS. There was a release by tantrums that caused bootloop, but he fixed it now.
Use ADB to go back to recovery.
@DFornazari
CM10 isn't heavy at all. rmcc committed a lot of changes from TI's branch and I think it caused some instability with the some of the newer releases. I based that speculation from a comparison between nightlies before the changes was made and after the changes was made. I didn't look at the code so I can't be 100% certain since I don't know what they changed. rmmc is a great dev and should have all the device specif bugs sorted soon.
Yes its all working fine now with cm10 m2 and regualr gapps but I have a new issue.
Whenever I try to download an app from the Play Market ( nova launcher, for example ) it pops up with an error reading:
"Error: 'Nova launcher' could not be downloaded due to an error (927)"
or alternatively:
"Error: 'Nova launcher' could not be downloaded due to an error ( error retrieving information from the server )"
Tried to install apps via online Play Store both on my phone and my laptop but the download never starts. Help?
Disregard that, fixed after reflash.
Hey all!
This questions is probably dev only, but since I dont have permission to post on dev thread, I had to pop out my question here. Here is the deal: from mid march I started building my own nightlies from CM 11 source and I use them only on my device. After 27.03, every time I flash a new nightly, my phone boots up but first I get 'Unfortunatelly, has stopped' and after that same message but for systemui process. Somewhere in CM 11 nightly thread I read that CM is now using msm8960 kernel, so I switched my builds to that kernel, but still have the same problems. If I do a full factory reset, phone boots ok with the nightly I flash, but as soon as I reboot it again, same story... I also tried with the recovery that is build with the rom itself (regular clockworkmod, 6.0.4.8, normally I use clockwork touch 6.0.4.6) still the same problem. But, if I flash the M5 release, it works with no problems... Did anyone encountered similar problems?