Database Users

CM 6.1 Stable

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

[Q] MT4G iced glacier; clockwork mod recovery problem

hey guys im having a big and really annoying problem i cant fix hopin in can get some help...
i have the iced glacier 1.1.6 with clockwork 3.0.0.5(rom managerv3.0.1.0). i want to make a backup nanDroid.. so i do and it completes and everythings fine... until i to the restoring part. after it "successfully" restores(yes, i did wipe cache, wipe dalvik, and even wiped eveything in everyorder possible. i restart my phone and it freezes on the mytouch 4g bootup logo. everytime. no matter what. it does let me reinstall the fresh ice glacier rom...
note: when i wipe the dalvik, its almost instantaneous wipe, like it doesnt do it?
there is an error about e:/ not mounted (sd-ext) or something close to that. but still says it worked.
things ive tried...
renaming the file.
moved the file.
reformatted SD.
wipe data...etc twice in a row to make sure it wiped.
any ideas?

You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse

i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...

drpepper4lf said:
i did the 2.5.1.2 first but it didnt work so i thought id try the newest one...but 3.0.0.6? where do i get 3.0.0.6? its not in rom manager. ( i really hate rom manager it never works for me...) and ive never done adb? or anything on my pc. everything ive done is on my phone...
Click to expand...
Click to collapse
Sorry I was asleep but if you still looking for the solution.
http://forum.xda-developers.com/showthread.php?t=952433
Go to option's thread and follow his instructions on howto install 3.0.0.6 as it works also.

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

Gingerbread 3.0

Where can I find the download link for the new gb.
Dinc

I'm not sure what you're asking for. Honeycomb 3.0 (which is not available for the Incredible) or Gingerbread with Sense 3.0?
Sent from my awesome sauce Incredible uisng Miui

I think gingerbread with sense 3.0. Sorry.
Dinc

There are several roms with what you are looking for in the development forum.

Oh ok. And do these install the same way. I'm still using the old clockwork recovery.
Dinc

Yes they should install like normal. Check the OP's for the ROM though. All require hboot .92 and CWM 3.0.0.x.
I recommend giving JoelZ's kingdm rewind 3d a go. very smooth

Yeah I'm still using the old cwm and I have never messed with cwm3 so how do I install the new newest cwm.
Dinc

You can use rom manager or you can flash the recovery manually in hboot. Files at www.dougpiston.com

RE: Multiple wipes
http://www.cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.

I only wipe everything once, flash vr superwipe, then flash rom. Works fine on all.
sent from whatever damn rom im using this hour!

k_nivesout said:
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
Click to expand...
Click to collapse
You obviously need to wipe three times and then flash the ROM twice. And reboot about 4 times. One each is not enough. Pull your battery a couple of times as well.

Is installing the new cwm the same as flashing a radio.
Dinc

If you take the time to read what I linked, it explains everything. When you're telling your recovery to wipe, it is a routine run within code. Doing a secondary wipe or even a third is just running the same exact command again. Logically, why would CWM run the same exact command differently, necessitating multiple wipes to get the same result?
There's no "randomness" built into the recovery that would result in the command not being run, or run differently, when you select it.
Its not like a physical action, where the more you wipe, the "cleaner" it gets. Again, it is a routine run within code, and it is not variable or random.
If there was any perceived benefit to the wiping procedure that you mentioned, I'm willing to bet that its due to wiping the /system and /boot partitions, which isn't done when you wipe data/factory reset and wipe cache in the main menu. This is something that should be, and usually is, included in the rom's updater script, but may be forgotten by the dev. Some people have mentioned that recovery version 3.0.0.8 does not work well with AMOLED incredibles. I can't speak for that myself, but in the event that there is a problem, the resolution would be using the 3.0.0.7 recovery, not wiping multiple times.
And I don't think you're correct in assuming that "all the devs" recommend the multiple wipe approach, I think you'll see that plenty do not, including the cyanogen dev who wrote the article I linked to (BTW, he is the one that got CM7 on the Droid X, a phone with a locked bootloader, so I'm assuming he might know what he's talking about.)
That is all..

snapper915 said:
Is installing the new cwm the same as flashing a radio.
Dinc
Click to expand...
Click to collapse
They are totally different, CWM is a recovery, radios are well, radios. They are flashed the same way though (in bootloader).

Awesome. Thanks. I don't have to rename any thing.
Dinc

cvbcbcmv said:
you mean like PB31IMG.zip? No, nothing like that.
Click to expand...
Click to collapse
Sweet. Thanks for everyone's help.
Dinc

Boot Loop Issue

Hi,
I am having an issue with my phone where the phone keeps on boot looping. I have read the brick guide and I tried the solutions in there but I am still stuck with a boot loop.I managed to install clockwork and cm 7.2 on the phone but it still boot loops and it has the good emmc chip as well. I also flashed the pd15img in hboot it doesn't return any errors and still loops. Any help/direction would be greatly appreciated. Thank you.
Glacier PVT Ship S-Off
HBoot-0.86.0000
Radio -26.03.02.26_M
eMMC-boot

make sure u have the correct .img. I got it from here. Did u make any backups?
try flashing the .img from the link. Follow "I - 4) Downgrading" I used 4b after that. so try that...it will help u get to stock froyo

Me too
trollimammoth said:
Hi,
I am having an issue with my phone where the phone keeps on boot looping. I have read the brick guide and I tried the solutions in there but I am still stuck with a boot loop.I managed to install clockwork and cm 7.2 on the phone but it still boot loops and it has the good emmc chip as well. I also flashed the pd15img in hboot it doesn't return any errors and still loops. Any help/direction would be greatly appreciated. Thank you.
Glacier PVT Ship S-Off
HBoot-0.86.0000
Radio -26.03.02.26_M
eMMC-boot
Click to expand...
Click to collapse
Mine boot loops with just about every ICS rom except (so far) the new chameleon one. It does the thing where if I get an incoming text when I try to check it it restarts the phone, and after a few days it boot loops permanently. What I mean by that is I'll try to use the phone and it's in the rom's splash screen just looping and looping and doesn't stop until I turn off the phone.. So when that happens I have to hold the volume down, turn the phone on, and wait until the boot menu comes up.. Then go into recovery and wipe data, cache, dalvik, and flash a new rom and gapps. It really sucks because I love PACman rom's and they boot loop the most.
Oh also my phone kept not booting once because my back button got stuck down.. So check your buttons too? Hopefully something there helps. I'm still trying to find out why PACman rom's hate me! Good luck!

Everybody please read the op in the developer's roms they all tell you to wipe cache/dalvik this what I do when I install any rom I throws out all the bugs and gets the rom moving normally
Sent from my HTC Glacier using xda app-developers app

that's not it..
aliamin86 said:
Everybody please read the op in the developer's roms they all tell you to wipe cache/dalvik this what I do when I install any rom I throws out all the bugs and gets the rom moving normally
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
That's not it.. I wipe my data, cache, and dalvik cache 3x before flashing a new ROM. I think the problem may have something to do with the kernel the devs are using because both Pacman and evervolv roms do it the worst, and I noticed Pacman is using evervolv's kernel. chameleons ROM doesn't restart or boot loop on me at all..

I had same problem. I installed 4EXT recovery and formatted everything ext 4 +full wipe.Then installed a different kernel other than stock.That solved all issues.
Sent from my HTC Glacier using xda app-developers app

Had success with factory data reset
Hello. I had the boot loop problem and tried everything (even the wierd twisting thing which worked for others, not me). I ended up fixing the problem by using the factory data reset solution. This is done by holding the power and volume up button until the screen lights up with options. Then select the factory data reset option.
THIS WILL WIPE OUT EVERYTHING except whats on your SD card. So you'll have to redownload all your favortie apps. But i actually liked that new phone feeling after the reset. Hope this helps someone.