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

HELP

Used this method to Root, unlock bootloader and get SU
http://forum.xda-developers.com/showthread.php?t=1202883
Flashed over CM7 beta, rebooted system, and I get stuck at the dual core screen. I think my battery was really low, because when I pull the battery, I get the "battery too low to flash". But its hard to tell when the battery is charging. Does it charge (AC) when I am in CWM? Or anytime when its plugged into AC?
IT dosent sound like a hard brick, just a soft brick perhaps. I hate rooting phones cause of this.

does not charge while in cwm but powered down it should charge

When I power down, and plug into outlet, it just boots up and stays at Dual Core screen with unlocked.
EDIT: Flashed a different ROM and it seems to be working fine. God damn Atrix and Cyanogen. Was never this hard on HTC Aria to do all this crap.

+1. BUT, you shouldn't need to flash, go into android recovery and factory reset and erase cache and reboot and you should be ok. I got stuck in boot loop the first timeI flashed CM7 prebeta 1 the first time. Good habit to wipe everything (except system) after installing ROMs.

Its backwards to me that you wipe everything AFTER installing ROMs.
But everything is working fine now.

It's just a precaution to make sure there is nothing to conflict with the new ROM

Phoneguy589 said:
It's just a precaution to make sure there is nothing to conflict with the new ROM
Click to expand...
Click to collapse
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing

Alcapone263 said:
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing
Click to expand...
Click to collapse
+1
I have one backup. I always manually format before flashing, personsally.
Sent from my MB860 using XDA App

[Q] Rebooting after flashing Rom

Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?

matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
Go back to stock first, and check if that has the same problems...

matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app

DenmarkRootN00b said:
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. I tried that as well, but Unfortunately, the same problem. I don't have a problem what so ever when I am using the phone while it is charging or plugged in, but as soon as I take it out, and even if it is full, it shuts off, tries to turn back on and it wouldn't, it keeps rebooting, once i plug the charger in it, it would stay on.
That tells me either:
The Battery is bad!
Or
There might be a circuit problem with the phone sucking power out of the battery!

Need help, please!

Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk

Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.

I also think there's a problem with your battery, it might need to be replaced.

ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk

Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.

norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?

Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped

[SOLVED] Nexus 4 not turning on after flashing latest faux kernel.

So I flashed mako-jb-kernel-028u-JWR on my nexus 4 and when I rebooted the notification light was flashing red. I booted back into TWRP and flashed mako-jb-kernel-027m-JWR to try and fix it. After I rebooted it was stuck on the boot animation with the flashing light. Whenever I started up TWRP the light would start flashing and the phone would turn off before I could reflash carbon rom. The light wouldn't flash when I was in fastboot . Now it won't even turn on, even if I plug it into power. I looked around and couldn't find anyone else with this problem. I'm assuming the battery ran out of power and I need to let it charge before I can do anything. Though last time I booted into TWRP the battery was above 90%. If someone could suggest something to do it would be great.

if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454

simms22 said:
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
Click to expand...
Click to collapse
I'm hoping I won't need to do that since I don't have a T5 screwdriver and I don't trust myself with manually charging a battery with a power supply.

I should also mention that I used this https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en about an hour before flashing the new kernel.

Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4

RASTAVIPER said:
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
The problem is that it won't even turn on. I think it ran out of battery and its refusing to charge.

Alright so I did some searching and found this post http://forum.xda-developers.com/showpost.php?p=43291951&postcount=27 I did that and my phone can actually boot up now. Also I should mention that you need to hold the buttons for EXACTLY 60 seconds or it won't work. I'll let it charge and attempt to reflash Carbon Rom after.

TWRP kept closing on me before I could reflash Carbon, so I restored to the stock rom and kernel using WugFresh's toolkit. I couldn't boot into the rom until I went into fastboot, went into stock recovery, and restarted my phone. Now I can boot up perfectly fine! Also I flashed the latest faux kernel again just to make sure it was the problem, and after flashing mako-jb-kernel-028u-JWR I got the red led again, So I'm advising everyone to stay away from that build.