Aloha all)
Need wipe before flashing next CM Nightly builds?
Thx
I am not sure if your question is clear or not,
anyways,
it depends, if you are coming from stock or another custom rom then YES.
if you are already on a nightly and you want to update to newer builts, usually a wipe is not needed. i said 'usually' because we never know what are the changes.....
Example) I have a cm_crespo_full-13. Need wipe before flashing cm_crespo_full-14?
zadnica said:
Example) I have a cm_crespo_full-13. Need wipe before flashing cm_crespo_full-14?
Click to expand...
Click to collapse
Nope, you only need to wipe when installing a new rom for the over a different rom.
kenvan19 said:
Nope, you only need to wipe when installing a new rom for the over a different rom.
Click to expand...
Click to collapse
Nice. Thx)
zadnica said:
Nice. Thx)
Click to expand...
Click to collapse
Np man, flash away!
kenvan19 said:
Nope, you only need to wipe when installing a new rom for the over a different rom.
Click to expand...
Click to collapse
This is somewhat accurate. But for the best possible performance it is recommended to wipe.
But yeah, pretty much... just flash it and if you encounter any sketchy problems. Perform a fix permissions (if FC's occurs)... or Wipe cache, factory settings, dalvik (then do fix permissions after restoring apps) before you make a thread about your problem.
Related
Im running sparksco cm7.2 and everything was going well, until I tried to backup. The system backed up but now im stuck on bootloop! Can anyone help with this? ive tried wiping and restoring and no luck. Stuck on bootloop, Damn!!!
letmeputdatipin said:
Im running sparksco cm7.2 and everything was going well, until I tried to backup. The system backed up but now im stuck on bootloop! Can anyone help with this? ive tried wiping and restoring and no luck. Stuck on bootloop, Damn!!!
Click to expand...
Click to collapse
Have you tired a fresh flash or flashing another rom/back up
Sent from my PG06100 using Xparent Blue Tapatalk
Boot CWM, wipe /system, /cache (cache), dalvik cache, reflash rom, reboot.
All good thank u! Just restored back to cyclonic! Let's Go Giants!!!
First time I've heard of something like this, maybe next time ask the developer of the rom?
VICODAN said:
Boot CWM, wipe /system, /cache (cache), dalvik cache, reflash rom, reboot.
Click to expand...
Click to collapse
That should work, but the roms do wipe cache and dalvik-cache for you already so it's going to take a long time to boot up. Also every aosp rom already wipes system before installing just a fyi.
sparksco said:
That should work, but the roms do wipe cache and dalvik-cache for you already so it's going to take a long time to boot up. Also every aosp rom already wipes system before installing just a fyi.
Click to expand...
Click to collapse
Actually not all roms wipe /system.. key ingredient here.
VICODAN said:
Actually not all roms wipe /system.. key ingredient here.
Click to expand...
Click to collapse
I didn't say all roms, you mis-read again, but it seems to be a typical thing for you to do.
sparksco said:
I didn't say all roms, you mis-read again, but it seems to be a typical thing for you to do.
Click to expand...
Click to collapse
You said every AOSP ROM wipes /system.
VICODAN said:
You said every AOSP ROM wipes /system.
Click to expand...
Click to collapse
Yes that's what I said. Can you show me one that doesn't? And it should be a mainstream rom too like cyanogenmod, miui ect. Just show me one mainstream aosp rom that does not wipe system.
sparksco said:
Yes that's what I said. Can you show me one that doesn't? And it should be a mainstream rom too like cyanogenmod, miui ect. Just show me one mainstream aosp rom that does not wipe system.
Click to expand...
Click to collapse
Oh Sparksco. I love you.
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
tomalrocks said:
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
Click to expand...
Click to collapse
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
tomalrocks said:
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
Click to expand...
Click to collapse
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
aypeeootrek said:
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Click to expand...
Click to collapse
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
tomalrocks said:
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
Click to expand...
Click to collapse
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
thnx123
yhnk you for
Zalithian said:
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
Click to expand...
Click to collapse
hehehe I already got that scare after flashing new rom and it was taking a long time to boot during first boot.
Thanks anyways
Dangit, guys, I hate to be an idiot, but I've looked and looked and cannot find what I'm looking for. I tried flashing pa and cm and aokp and every time I flash the aosp keyboard force closes and almost every other app just won't open. Again, I apologize if this is common knowledge it if I have missed it, but I for the life of me can not find a solution. I came from a GNex, and everything was just so simple about flashing on that. Thank you in advance to anyone who can and will help.
Did you check the md5 on the roms before flashing? And are you fixing permissions after you flash?
x714x said:
Did you check the md5 on the roms before flashing? And are you fixing permissions after you flash?
Click to expand...
Click to collapse
To add onto this, what options do you select to wipe the phone prior to flashing these roms?
Yes and yes. Weird thing is I tried it on my wife's s3 and same result.
Which GAPPS package are you flashing for these JB 4.2 roms?
SlimSnoopOS said:
To add onto this, what options do you select to wipe the phone prior to flashing these roms?
Click to expand...
Click to collapse
I wipe everything. Cache, Dalvic, Data, System. Thrice.
SlimSnoopOS said:
Which GAPPS package are you flashing for these JB 4.2 roms?
Click to expand...
Click to collapse
gapps-jb-20121212-signed.zip from goo.im
techarlj said:
gapps-jb-20121212-signed.zip from goo.im
Click to expand...
Click to collapse
Make sure you have matching gapps for the rom version. 4.1 gapps for 4.1 and and 4.1.x and 4.2 gapps for 4.2 roms
After I threw up in my mouth a little bit... I realized i don't have an iPhone
Hey Guys, Monday evening, i guess, i'm gonna receive my Nexus 5 32GB White... Well my question is:
After unlocking and rooting, I want to install Catclysm Rom + Franco.Kernel If i delete the Boot.img file inside the zip of cataclysm rom and replace it with the franco's img will it work?? will i have Cataclysm and franco.kernel at the first boot?? So i don't have to reboot again to flash the kernel
Thank you guys for your help
p.s.: In future when cataclysm will get another update, do i have to wipe evrything or just cache and dalvik?? (Before flashing i'll delete the boot.img file inside the zip so i won't loose the kernel)
p.p.s.:Maybe i'm crazy but i need to know these little things xD
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
viking37 said:
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
Click to expand...
Click to collapse
Really thank you man, you solved all my questions I know it's not hard to flash the kernel separately but i'm lazy xD
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Enri1196 said:
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Click to expand...
Click to collapse
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
viking37 said:
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
Click to expand...
Click to collapse
Again thank you, i also pressed the thanks:good: button for all your other answers
OK, newbie here.
I've had my TF300T for around 2 years (or maybe its just one )
Anyway, I finally broke down and unlocked, rooted and applied the latest Omni ROM to my system without issue.
So far I like it just fine but would like to explore other ROM's as well.
Being a newbie I'm sure if this is some simple question.
Can I just flash my system with a CyanogenMod ROM without doing anything else?
I am using TWRP which seems rather easy to use.
Forgive the newbie question as I'm still learning all the parts and pieces of all this.
Cheers
Did you install the kitkat version of OmniRom? If so, then you can install the KitKat version of Cyanogenmod without a problem. The TWRP version for Jellybean is different than the KitKat version.
Sent from my TF300T using xda app-developers app
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Yeah, I installed the kitkat version of OmniRom so I was thinking it would be OK to install CyanogenMod after doing a wipe first.
Thanks!
ChiefIlliniwek5 said:
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Click to expand...
Click to collapse
Yeah, you shouldn't ever dirty flash anyways though unless you are just updating nightlies. From ROM to ROM dirty flashing is a no-no and could result in FCs or bootloop unless you wipe data.
ChiefIlliniwek5 said:
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Click to expand...
Click to collapse
Can you define clean flash?
Other than Dalvic Cache and Cache what other things need to be wiped to constitute a clean flash?
ricktendo said:
Can you define clean flash?
Other than Dalvic Cache and Cache what other things need to be wiped to constitute a clean flash?
Click to expand...
Click to collapse
Wiping /data & /system