so i had been running my nexus 5 with cataclysm ROM for a while.,today i decided to do a cm12 nightly flash ...i worked well it booted fine, everthing worked well ,flashed gapps ,tibu,restored my apps .now after a reboot i kept getting "system uid inconsistent " errors.I (like a idiot) tried "fix permissions "in TWRP which resulted in a boot loop.so i decided to flash cataclysm rom freshly again.It worked well but now sometimes i get force close errors like "android.process.acore" and sometime google playstore force closes.
i am scared i might have spoiled something,
also the cm12 nightly reflashed bootloader as it was 5.0.2 and also radio ,do these things cause something to break??
how do i return to normal??
I have updated my Radio while I am still using Cataclysm and I didn't face any of the problems you mentioned above. I have also switched from Cataclysm to other ROMs (including CM12) and back couple of times in between and never faced any problems.
I generally wipe everything except Internal Memory when switching ROMs. Did you do the same?
Yes,its a clean flash.
Just a question has this got something to do with the "fix permission" thing I did in TWRP?
Even though I wiped and flashed cataclysm later??
Also I googled around .does a corrupt data partition cause these kind of errors to pop up??
Currently the occurrence of these errors is rare but I've notice reccurent notifications from google playbooks even after I remove the notifications they reappear after some time .
I've decided to use my nexus 5 for a while and see if the problems are reproducible .
But I feel like the only wrong thing I did was "fix permission " in TWRP other than that its was just regular ROM flashing.
Yes... a corrupt data partition might cause this.
Generally I wipe the following when I am flashing a new ROM:
Dalvik Cache
System
Data
Cache
As you see I wipe data as well when I am moving to completely different ROM.
Does that mean my device is not fit for flashing new Roms anymore.?
How can I fix my data partition to be as good as new??
No... What I meant was to wipe the Data partition as well before flashing a new ROM. Wipe all the partitions except the Internal Storage partition. (Note: Data and Internal Storage are not the same)
If that still doesn't work, try flashing the factory image to rollback to stock. Then again flash the recovery and try flashing a custom ROM.
You might try just reflashing the CM12 nightly and see if that fixes it. Otherwise you'll have to flash from fresh. I wouldn't recommend doing a full backup restore if possible.
Related
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.
So I regularly flash CM10 and AOKP nightlies daily, on occasion switching between the two. Because I am flashing from jelly bean based ROMS I do not need to wipe my /data partition. Does this slow the device down? It is a Samsung GT-P3113 if that helps
Hmm.
I dont think so but I think doing a fresh wipe is better.
Without wiping you might get some errors or something.
Yes, but if you flash an upgrade of your currently Rom no.
If its simply an update from your current ROM, there should be no slowdown. The /data partition contains basically what your phone identifies as "available internal memory"
If you flashed a different ROM or a GB to ICS ROM without wiping data it actually won't slowdown the device, just mess up the operating system with errors FCs, and maybe cause a bootloop.
Sent from my MB508 using xda premium
Yesterday i flashed and booted no prob. Then went backan flashed the same custom rom twice just out of curiousity and ended up with bootloops. After wiping and reflashing had no probs again. Thats not the first time ive had probs by not wiping either. Seems like its just good practice to wipe whenever possible.
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install
I was on CM10.1 for a very long time, and just recently decided to flash something newer. So I tried flashing Philz recovery (had CWM), then used that to flash VRUBMF1 and VRUCML1 baseband afterwards (from this thread). Without booting my phone, I then flashed CM11 and the kitkat gapps. When trying to restore apps through Titanium Backup, I got a random reboot. Since then, I would get many random reboots, most often in the middle of a Titanium Backup restore of my user apps because it's the first thing I want to do. Sometimes the phone will reboot before even getting to the app restore. I have tried flashing PAC rom (4.3--I flashed jb gapps with this) and unofficial Paranoid Android (4.4) as well, and the problem persists no matter which rom I am running. Of course, I have tried reflashing many times.
I am also trying and currently on TWRP, but this hasn't helped. Going back to CWM and trying to restore my CM10.1 backup gives me a fail error.
Before each flash, I wiped data, and rewiped cache and dalvik afterwards too. Is there a problem in my flash process? What can I do to solve this issue?
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.