I did the veryGreen install using the latest stable and the first time I had issues so I did a clean install today. I finally got a recovery menu but after I wiped davlik cache it booted into the regular NC OS while the memory card was still inserted. I shut it down and CM7 started up and after I moved the ring to unlock the device it rebooted back to NC OS once again. Shut it down again and CM7 loaded just fine. Anyone have any ideas on why it did this? Thanks.
Maybe somthing is on ur SD card and keeps reading off it
HTC Wildfire S (VM) "s-off" "rooted" Stock Rom
How did you actually "wiped davlik cache" when running CM7 off uSD?
votinh said:
How did you actually "wiped davlik cache" when running CM7 off uSD?
Click to expand...
Click to collapse
I did a clean install so I formatted my uSD using one of the programs suggested here. I did my veryGreen install and everything seemed okay.
Reading around everyone keeps saying clear davlik cache if you are having force close problems. So I rebooted in Clockwork Recovery and I used the volume buttons to go to the option to clear davlik cache. On my prior install I couldn't even get the menu to come up.
I have been playing around more and as long as I shut the NC down it works fine. But if I try a reboot it boots up the NC side now.
what version of cm7 are you running? sounds to me that it might be buggy
jsnake said:
I did a clean install so I formatted my uSD using one of the programs suggested here. I did my veryGreen install and everything seemed okay.
Reading around everyone keeps saying clear davlik cache if you are having force close problems. So I rebooted in Clockwork Recovery and I used the volume buttons to go to the option to clear davlik cache.
Click to expand...
Click to collapse
Those steps are only applied when running CM7 on eMMC, not off the uSD.
O sorry for the bad info! He nos more then I do
HTC Wildfire S (VM) "s-off" "rooted" Stock Rom
Related
Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com
Hey yall I'm having a problem with my Aria. I formatted my micro sd and wiped the phone to start with a clean slate. I downloaded CM7 RC2 from the CM website and i also downloaded gapps from there as well. but when i installed RC2 and gapps it would start up normally then when i would try to use the setup wizard it would freeze once i touched the android guy and would go into a boot loop. i recorded a video to help explain what im talking about. could it possibly be a corrupted version of gapps? cause i tried installing just rc2 and it worked fine....
http://www.youtube.com/watch?v=iZWiYGHh8LQ
Was it plugged in while in recovery?
yes and no. i didnt have it plugged in the first time around but the second time i did. and i did a factory reset, cleared the cache and the dalvik cache
Try re downloading the rom and gapps file. Make sure phone is unplugged and wipe data and caches again and then flash again. Ghats what I would do.
Army_Spec_Ops said:
Hey yall I'm having a problem with my Aria. I formatted my micro sd and wiped the phone to start with a clean slate. I downloaded CM7 RC2 from the CM website and i also downloaded gapps from there as well. but when i installed RC2 and gapps it would start up normally then when i would try to use the setup wizard it would freeze once i touched the android guy and would go into a boot loop. i recorded a video to help explain what im talking about. could it possibly be a corrupted version of gapps? cause i tried installing just rc2 and it worked fine....
http://www.youtube.com/watch?v=iZWiYGHh8LQ
Click to expand...
Click to collapse
Sounds like you might be using the wrong gapps. Double check you got the right one.
Sent from my Liberty using Tapatalk
You're almost certainly using the wrong Gapps.
Get the right one from here
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.
DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.
you didn't wipe dalvik in advanced, do that and bootloop will stop...
darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...
when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.
DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.
Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.
I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6
I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App
Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.
Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue
no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.
I'm stuck on a friend's nook.
I've flashed mine about 100 times no problem.
I've put cyanogen on two other nooks no problem.
I'm doing something wrong with this one I guess.
I have a bootable CWM micro SD and I can boot to it no problem, I'm trying to flash the latest nightly.
What I did up to now was flash the repartition data and reformat data zips.
Then I formated system, data and cache.
Then I flashed cyanogen.
I got it to load cyanogen one time!
But when I rebooted I could never get it to load again.
Since then I have formatted the boot and flashed a few different boot fix files.
I'm stumped.
When I boot it now it goes to the green Cyanogen mod banner, than a second later it says 'loading' under that, then it goes to a black screen. I have to hold the power button down for 15-20 seconds after that to shut it off.
So I have a nook that I can boot to CWM v3.2.0.1 from a micro SD card.
What steps should I take to get this thing working again?
What I did up to now was flash the repartition data and reformat data zips.
Click to expand...
Click to collapse
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
patruns said:
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
Click to expand...
Click to collapse
Tried that, Now I get 'Read Forever' then a quarter second of the 'N' screen that is Grey then turns a sort of washed out in orange color for a half second, then a message screen that says: 'Install Failed' over a picture of a nook with a red exclamation mark on the screen and 'Please power OFF and back ON again. If you continue to have issues please contact Customer Support or visit www.nookcolor.com/support' Then the device turns itself off.
I had gotten that screen a couple of times leading up to this. Got rid of it by flashing some boot fix files or something.
Something is wrong with the loader or some boot data or something I don't know about.
Can anyone give a step by step on how to take a Nook down to a clean slate then build it back up so I can boot Cyanogen nightly?
I can Boot off a micro SD into Clockwork Recovery.
Those were the steps I took to restore and deregister a Nook recently before returning it for a replacement. However, I never messed with the partitions. Someone familiar with the partition structure will hopefully chime in.
Bump having the same issues. Just started today.
Mine works if I leave it charging, As soon as I unplug it..it turns off.
CM7 and 1.3 ROM hang ups
patruns said:
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
Click to expand...
Click to collapse
First tried to install final CM7.1.0 over nightly. Followed instructions here on Opening page Nook Color Android Development thread for this and then tried step-by-step Maurice Mongeon - Nook Color: updated Clockwork Recovery Bootable SD page. I left a similiar comment to this post at his page. Scroll up to see his instructions.
http://mrm3.net/nook-color-how-to-install-cyanogenmod-7-1/#comment-1069
From his site: Everything good from ROM Manager making sure latest CWR 3.2.0.1 until reboot into recovery. Get dark purple-black screen, have to power+n force it into internal CWR 3.2.0.1. Gets through Install from sdcard complete. Mounts and Storage > format /cache > Yes – Format gives me Error Formatting /cache!.
If I try format /system… it hangs. Reboot into CWR again it hangs again at Formatting /system… No way to format system, data, cache from Mounts and Storage to boot into clean new ROM!
I can use – wipe cache partition and – advanced > Wipe Dalvik Cache instead afted installing – update-cm-7.1.0-encore-signed.zip (correct checksum) from sd-card. Everything goes OK except it boots back into CyanogenMod-7-08192011-NIGHTLY-encore.
Restoring previous Nandroid from internal CWR or SD CWR also hangs at restoring /system. What should I do? Can not update or get it back to original 1.3 ROM either? Lockups and errors in Mounts and Storage formats stop me! Tried suggestions in this thread using the boot SD version of ClockworksMod Recovery, none of them seem to work. Anybody have any suggestions as to what to do next?
@ Izord and lschroeder.
If you guys absolutely cannot get it going with CM7, I then suggest trying to get back to the original, stock ROM.
If you had formatted /boot, then I cannot help since I never did mine so I don't know for sure but if not, you should be able to bring the NC back in the original stage.
votinh said:
@ Izord and lschroeder.
If you guys absolutely cannot get it going with CM7, I then suggest trying to get back to the original, stock ROM.
If you had formatted /boot, then I cannot help since I never did mine so I don't know for sure but if not, you should be able to bring the NC back in the original stage.
Click to expand...
Click to collapse
I can not get to stock ROM either, format/system... hangs and I have to hard reboot.
Question for anybody: Can I use ADB or adbWireless to help get around the format/system... error and install CM7.1.0 or Stock 1.3?
Sorry to resurrect an old thread but this is the only place I've found that describes my problem. I'm experiencing the exact same thing with my Nook Color and followed the exact same suggestions without success.
Was this ever resolved? What finally made it work?
This is exactly what is happening to me. I've already posted my problem to another thread but I thought I would comment here in case this thread finds a resolution.
BTW, my thread is http://forum.xda-developers.com/showthread.php?t=1578127
after i have installed CM7 it was missing markets so i try to go to recovery menu but not work so i install recovery menu system after that my defy only start at CM7 logo and nothing happened after not working at all helllllllllllllllllllllp?
Think you need to restart.
And remember this time, flash gapps after installing CM for your market to come back
I don't think you're supposed to install any kind of recovery from within CM7 since supposedly there should be one already.
You can always try the SBF flashing route, but don't do that if your battery is low.
glycolysis said:
I don't think you're supposed to install any kind of recovery from within CM7 since supposedly there should be one already.
You can always try the SBF flashing route, but don't do that if your battery is low.
Click to expand...
Click to collapse
He´s right... you´ve damaged your recovery, so there is no other way - you have to start from flashing froyo again.
CM7 has its own boot menu so you are not supposed to install any boot menu or 2nd init after that. If the boot menu is corrupt only option is to start from scratch Froyo SBF.
Read FAQ of CM7. Install CM7>Install Universall pack of Google apps from link on CM7 threat and if it stuck on CM7 logo wipe cache partition and dalvik, don't wipe data and then wait few minutes for build everything. If it stuck still reboot phone on battery. It works for me.