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.
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'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
ive been running into a strange issue installing roms lately. I can install anything touchwiz no problem and they run great. but for some odd reason if I install any of the numerous aosp roms the just hang on first boot. ive tried almost every aosp there is and they all sit there and hang, ive even let a few sit for hours with no luck. yet touchwiz will boot fine in just a few minutes. anyone have any suggestions or ideas?
Have u done a clean wipe factory reset wipe delvk catche.. Wipe everything clean.. Some stuff from the tw roms could stay behind.. Wen ppl change from aosp rom to a tw rom they use synergy rom cuz it does a clean install .. I could be wrong about this
Just be sure to wipe data/cache. The ROM zip install erases system for u.
Sent from my SCH-I535 using Tapatalk 4
Erasing data problem
I have unrooted Verizon S3.
It was working ok until I decided to put some new ROM. I instaled Synergy S3 r420 rom. It worked OK, but did not have mobile internet. WiFi and mobile hotspot were working fine. I decided to put back my old system, not to mess around any more, and went into CWM mode.
After entering CWM I tried wipe out/factory reset but it stacked at Formatting /data
Previous formating of cache and wiping of Dalvik went OK.
Part of the message was E:unknown volume for path [sd/ext]
What di I done with my phone? Is it soft bricked or what?
I can still boot last ROM, and is functional
How can I return my phone to the state saved in my CWM backup ?
Thanks!
EDIT
I have tryed to instal a different ROM - Hyperdrive, and install went normaly. At the end asked me to reboot and I said OK. Then, upon rebooting, a Warning message appeared warning me that non Verizon softvare is detected and that I should take the phone to them.
Is there anything to do to reverse this state?
You need to use odin to restore stock
Sent from my SCH-I535 using Tapatalk 4
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.
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.