I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
1. So I first tried to uninstall that app with Rom Toolbox. Didn't help.
2. Then I cleared data and cache from Phone services. Didn't help.
3. Then I booted to recovery and wiped cache. No help.
4. Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
5. So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Yep, wiping everything is clean flash, or wipe everything but internal storage (if still problems, delete . Android folder beforehand).
Sent from my Pixel using XDA-Developers Legacy app
simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
for mw to be clean i would flash stock firmware then do the following procedure here
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606
simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
rob rich said:
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
Click to expand...
Click to collapse
OK, thanks. Maybe in my step 4 above I thought that factory reset was enough but I didn't notice that it does not wipe system. So I went too far and wiped all my data, too.
But earlier when I have flashed different roms and they always tell that you must do clean flash, I didn't wipe system. So I thought clean flash was just factory reset. Still those different roms were working ok. Next time I try to remember wipe system also.
Related
Sorry, this might be kind of a noob question, but i see build 23 is out for CM7. If i flash the new build, do i need to totally set up my phone all over again?
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Genocaust said:
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Click to expand...
Click to collapse
Thanks. Ugh, i didn't even think about that when i flashed CM7. Seems like it is a real PITA to wipe every time and have to configure all the settings again.
I had good success on my move from stock -> Ice Glacier (un-crapwared stock) by making a full TitaniumBackup of -everything- and then restoring it app by app (along with settings). They are similarly built ROMs, and it worked well for me with minimal downtime. You may want to consider trying that if you are just changing between CM flavors, as I would presume they are mostly backward compatible with a few fixes/features here and there. At worst it may leave you with just system settings to redo.
When i flash a new CMNightly all i do is wipe the cache and the Dalv/Cache and i've yet to have any problems. If you are worried about wiping and restoring everything. you might want to look into Titanium Backup.
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
shortskoolbus said:
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wiping the Cache and wiping the Dalv Cache will not reset the phone. Only a full wipe will do that.
To my understanding, a "full wipe/factory reset" in Clockwork Recovery will only clear /cache, /data, and Davlik cache. /boot and /system will not be touched. Some users moving from Froyo to Gingerbread have had problems with /system, and a wipe of /system (from within Clockwork Recovery or from adb) has solved some problems for people, beyond what a full wipe can do. Discussions are in the CM7 thread in the Application Development subforum.
I know, most people refuse to search for anything.
i usually wipe the Cache and the Dalv Cache when updating nightlies, but several times i've wiped nothing and just flashed the new one on top and its always worked just fine for me
I always do a full wipe when installing roms. Setting it up each time makes me think its a whole new phone which is cool.
You do NOT need to wipe when upgrading to a new version of the same ROM. I've probably flashed 10 no-wipe updates of cm7 on my phone and it's still perfectly stable, no force closes or anything.
Boot into recovery and wipe cache and dalvik cache before flashing. Give it a few mins to "settle" on the first boot, reboot again and you're good to go.
Worst-case scenario you'll just wipe and reflash anyway, and nothing lost.
I have been trying the new ICS ROMS and have an interesting observation to share. I have had many weird problems like the shutdown reboot issue, touch key lights staying on, force closes etc. The only time I had a clean install (without even the shutdown issue) was when I first used CWM to wipe everything and then used the stock (gingerbread) 3e recovery to perform another wipe before flashing a ROM. Anyone willing to try and confirm?
when u say another wipe using stock recovery, u mean just a factory reset, before reflashing cwm and then ics? becuz if so, ive tried that, and it was still hit and miss
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
rushi.1986 said:
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
Click to expand...
Click to collapse
It seems like there isn't an easy fix that works for everyone (for the shutdown freeze bug anyways--this was the one problem I just couldn't get rid of until just a couple days ago). I had a theory that Darkside superwipe was screwing it up for me (the method you use as I've quoted was basically my method for wiping prior to flashing any roms, with the exception of using 3e recovery).
Seanzscreams new Sky ICS rom claims to have fixed the shutdown issue for good. I don't know if this is true for everyone but it seems to have worked for me.
What I do is:
Flash darkside x1
factory reset x5
wipe cache x5
wipe dalvik x5
format system x5
Flash radio
wait 1 minute
flash rom
wait 1 minute
reboot and don't touch phone for at least 10 minutes
I've noticed that some people go to the extreme when it comes to wiping....... Super extreme.
I've always in my YEARS of flashing roms (I got G1 on day one), I've always done just a simple format of data and cache. Normally don't get any unexplained errors or bad flashes.
LOT of the problems rise from users. Either installing something that is buggy or just not following directions.
Restoring backups is probably the BIGGEST CULPRIT OF ALL. Often times, people just restore files that they shouldn't. Adding themes, adding animations, boot animations blah blah blah...then blaming devs because so and so is not working.
I use restore but I'm selective about my restores. I don't just restore everything that I just backed up. Has NEVER caused me any problems.
Hi, I recently rooted my LG Optimus Black (P970) and flashed the Surpressed ROM. Everything is working fine, but whenever I set the time to use network-provided values the clock goes to the wrong time.
Most of the researching I've done on this has pointed towards people not wiping the cache when flashing a new rom.
I wiped the cache and dlavik cache before flashing Surpressed V7, then flashed the updates immediately after (7.1, 7.2, 7.3, 7.5). I DID NOT wipe the cache before installing the updates, assuming it wasn't necessary because I literally flashed V7.0, rebooted, flashed the 7.1 update, rebooted, etc. until 7.5 was installed. Was it necessary for me to wipe the cache between updates?
I have wiped the cache and dlavik after installing 7.5, but that didn't solve my problem. Just wondering if anyone has thoughts about what I should do next. Should I wipe the caches and install 7.5 from the SD again? or do I have to do a factory wipe and restart at flashing 7.0, then flash the updates (wiping cache in between each)?
Thanks in advance for any help!
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
steven8590 said:
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
Click to expand...
Click to collapse
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
srix9 said:
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
Click to expand...
Click to collapse
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
srix9 said:
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
Click to expand...
Click to collapse
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
srix9 said:
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
Click to expand...
Click to collapse
And it looks like I spoke too soon. The clock is currently 3 hours 45 minutes behind the actual time. With it being off by that amount I would assume that it isn't a timezone issue. I will try wiping the cache/dlavik, reinstalling Surpressed 7.5, wiping cache/dlavik and rebooting. Will update on that once I have it running for a while. In the meantime, any other thoughts are more than welcomed!
Hey everyone. I have a rooted HTC One S. I downloader ROM Manager and downloaded CM10. i installed it, but on startup, the CM10 boot animation just keeps going and going. the longest i let it go was close to 20 mins. I'm pretty sure tht this shouldn't be happening, any thoughts or suggestions would be nice.
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
xXFlippyXx said:
have you followed all those steps: http://forum.xda-developers.com/showthread.php?t=1889339&highlight=cyanogenmod
?
most important thing is to wipe your system partition / dalvik cache.
if coming from another rom (stock or whatsoever) you need to do a factory reset too.
back up your data before, cause it will be gone then.
Click to expand...
Click to collapse
A wipe was all that needed to be done. The problem was ROM Manager wasnt wiping prior to installation. Thanks for the help, +1.
I installed the ViperRom and it worked great for a few months and then it just started resetting and erasing all my settings. This happened 2 or three times a week. In recovery I did a factory reset and installed CleanRom and now most of my apps force close and it happens both in dalvik and art. I ran permission fix but that did nothing. I did a factory reset again and installed a stock rooted rom and still have the same issues with apps force closing on me. The apps in break, google maps, google calendar and some other random apps. I have the bootloader unlocked with TWRP recovery.
BroncoAG said:
I installed the ViperRom and it worked great for a few months and then it just started resetting and erasing all my settings. This happened 2 or three times a week. In recovery I did a factory reset and installed CleanRom and now most of my apps force close and it happens both in dalvik and art. I ran permission fix but that did nothing. I did a factory reset again and installed a stock rooted rom and still have the same issues with apps force closing on me. The apps in break, google maps, google calendar and some other random apps. I have the bootloader unlocked with TWRP recovery.
Click to expand...
Click to collapse
Did you make sure you wiped system and data?
I would do a compelete Data wipe and sideload the ROM.
scrosler said:
I would do a compelete Data wipe and sideload the ROM.
Click to expand...
Click to collapse
+1 on this. Backup your internal memory, format everything in TWRP, reboot back into TWRP, then sideload the ROM.
There's always a little something left behind when wiping. (Get you minds or of the gutter...)
In your place I would RUU back to stock, full boot and then a factory reset from stock recovery. I had an issue with htc droid dna where it couldn't connect to 3g data, at that time I flashed every available rom, radio and kernel trying to fix it, I wiped several times from custom recovery. It got only fixed flashing a stock rom along with stock recovery and then factory reset.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Thanks for the replies. I wiped everything last night. The phone had nothing on it. I reflashed stock rooted rom. I still have the same issue. I will try the flashing the RUU and go from there.
I wiped everything again and flashed the nV rom. Everything seems to be working fine now.