Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
I read everywhere that the safest way is to do a full wipe, and since you have nothing to lose it won't hurt, so i think you should.
nickos12 said:
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
Click to expand...
Click to collapse
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
so i sould install the nighlty without wiping?
TechnoSparks said:
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
Click to expand...
Click to collapse
so i sould install the nighlty without wiping?
nickos12 said:
so i sould install the nighlty without wiping?
Click to expand...
Click to collapse
Yes you may
Ok thanks
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
TechnoSparks said:
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
Click to expand...
Click to collapse
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
giannisv6 said:
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
Click to expand...
Click to collapse
Yes, nightly is a daily release where changes are huge in the back end.. Sometimes a simple change can make a build unbootable. Sometimes it introduces new bugs. Sometimes it is better and fixes everything. It is of course a good thing to update to the latest if possible, it is just that it is also vital to know what we're going to face when we flash a new update. So that we can make backups beforehand in case something really bad happens.
If you are installing an update to the same ROM there is no need to wipe anything. Wiping is optional.
↑ Note, if you are reverting to a previous build, you will need to wipe everything as there will be conflicts for the system data. This is why frequent/periodic app backups useful.
You can do either both of them without any problem
Thank you very much.
It's the first time i flashed a custom rom (the AICP 10 successfully :cyclops: ) and i got overwhelmed with all these endless customization options .
Related
Sorry if I'm repeating a question that's already been asked but I couldn't find the exact answer I was looking for.
I want to update from the last 6.1 nightly to CM7 (current nightly) and I've loaded the newest version of CMR (3.0.0.5)....now what do I need to wipe when installing the new ROM?
I'm not too worried about backing a whole lot up, just want to load the new ROM to try it.
Any/all help would be appreciated.
Thanks,
jamierob
jamierob said:
Sorry if I'm repeating a question that's already been asked but I couldn't find the exact answer I was looking for.
I want to update from the last 6.1 nightly to CM7 (current nightly) and I've loaded the newest version of CMR (3.0.0.5)....now what do I need to wipe when installing the new ROM?
I'm not too worried about backing a whole lot up, just want to load the new ROM to try it.
Any/all help would be appreciated.
Thanks,
jamierob
Click to expand...
Click to collapse
Here you go http://romrepo.info/wiki/index.php?title=Install_from_another_ROM
I found the answer I was looking for.....
http://androidforums.com/sprint-hero-all-things-root/282179-cm7.html
Thank you for the quick reply!!
Thanks..... I got that working well. Now, if I just update to another nightly, do I still wipe all that or just what I was wiping when going from one nightly to another in CM6?
Thanks again,
jamierob
If you are updating you probably won't need to wipe, however I wipe cache and dalvik when updating
first off let me say im a newbi and just started flashing roms, and just wondered how i should go about updating a existing rom in ss3. i just need to know if i should just flash the new zip over the same rom slot or do i need to wipe everything and pretty much make a whole new rom? sorry if its a dumb question but i just cant seem to find a step by step answer to do this, and just so u know your answers are much appreciated.
adizzle23 said:
first off let me say im a newbi and just started flashing roms, and just wondered how i should go about updating a existing rom in ss3. i just need to know if i should just flash the new zip over the same rom slot or do i need to wipe everything and pretty much make a whole new rom? sorry if its a dumb question but i just cant seem to find a step by step answer to do this, and just so u know your answers are much appreciated.
Click to expand...
Click to collapse
You are fine to flash a new build over an old one without wiping data. Just wipe cache and dalvik cache, flash the new build, reboot and your good to go. The exception is if you are moving to a new version of android (CM9 to CM10) or if you are moving to a different ROM (CM10 to AOKP). In those instances you would want to wipe data as well.
Droid 4 - AOKP JB
Thanks, I do appreciate it. that's what I was thinking but you always want to be sure when doing this kind of stuff on your device.
sent from my droid 4/ cm10.
Hello, I have had a touchpad for some time and but CM9 and CWM on it some time ago, but it started having some issues recently. So I figured I should try and reinstall a newer version of CM and start from scratch.
I went to this post http://forum.xda-developers.com/showthread.php?t=2026692 and downloaded both the skz+tenderloin-1.10.zip and the gapps zip.
I then placed those into the Download folder on the touchpad.
This is where things took a turn. I rebooted to get into CWM, upon selecting it from the boot menu it kept restarting back to the boot menu. After a few tries it got into CWM. I then wiped the data and did a factory reset, wiped the cache, and then wiped the dalvik like the post said to do. I then went to install zip from sdcard. Found the skz+tenderloin zip and chose to install that. CWM says it starts to install but then before the progress bar fills up at all...it resets back to the bootloader.
At this point I am at a loss with what to do and I would really appreciate any help I can get with this.
UPDATE: I figured starting from scratch would be the best bet, so I have uninstalled CM9 and CWM using ACMEUninstall. Now I am wondering if it is worth using CM10 as my default Android or should I stick with the best CM9.
Either way, if I should use CM9 or 10 can someone either help me or point me in the right direction for the best tutorial on doing this properly?
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
sstar said:
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
Click to expand...
Click to collapse
The issue I am encountering is there is a ton of info out there, some outdated some not. I restored back to stock webOS with nothing else. I have ACMEInstaller 3 in the Palm directory, so I am ready to install the most stable/best CM9 currently out there, I just don't know which tutorial is the best one to follow. Could you perhaps just link me to one you recommend?
http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-232013/
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I installed CM9 based on the link above with the AIO package. It worked flawlessly, hopefully my freezing/restarting issues happen less often now. Thanks to all who offered help.
Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I can tell you that I use my Schizoid as my daily driver, and it's not a preview.
Hey guys,
I'm currently running CyanogenMod 10.1 from last week, very impressed with it!
I see there is a new version which fixes Deep Sleep.
Could someone please be kind enough to confirm the update procedure?
Flash the latest [LATEST][07/26] BETA CM10.1 + 3.0.50+ KERNEL while in TWRP, then flash the CAM-FIX2.ZIP. (no need to restart between both?).
Also, do I need to clear any wipe anything?
Will I loose any aps? or data?
Thanks so much for your time.
All I would suggest doing is wiping system, cache, and dalvik, then flashing it. I heard that the cam fix is the entire ROM, so u may not need to flash previous deep sleep fixed version first, you should know right away though because the zip file would be at least a few hundred mb if its the full ROM. Also I believe you will also need to flash the gapps again, you won't lose any of your stuff but u may have to sign back into the Google store again. If anybody sees this and wants to add on to what I said or correct me please feel free to. I haven't updated mine yet because I don't use base cm that hashcode releases, I use jesters, and as such I haven't ever updated my cm os before, but I am versed in the procedure. Anyways good luck!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Considering the deep sleep fix is kernel related, you can probably get by with just flashing it over your existing ROM.
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
you wipe cache and dalvik cache then you flash rom on top.
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
bober10113 said:
you wipe cache and dalvik cache then you flash rom on top.
Click to expand...
Click to collapse
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
youdoofus said:
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
Click to expand...
Click to collapse
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
bober10113 said:
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
Click to expand...
Click to collapse
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
youdoofus said:
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
Click to expand...
Click to collapse
If I were to go to advanced wipe when flashing a new build if I were to leave data option alone. Will that keep all of my data or not?
edit:
@R77
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
bober10113 said:
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
Click to expand...
Click to collapse
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
youdoofus said:
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
Click to expand...
Click to collapse
did i make it sound like i was replying to you?
guess i should have quoted him to make it obvious.
and again, if he's on rom A 1.0 and wants to upgrade to rom A 1.1 then no need to clean wipe or del android folder each and every time.
have you ever had an OTA ? samsung dosent wipe clean ure device just because u upgrade. so his question regarding a similar scenario would apply, dirty flash would work fine.
and again as stated before, if there is weird stuff happening then just clean wipe. no need to get nuclear each and every time.
btw various rom builds require clean flashes because they suppose people are coming from other roms. not saying that there aren't situations where continuously dirty flashing the same custom rom all along its progress wouldint eventually mandate ir benefit from a clean flash but i know of no one that clean flashes each time their rom dev updates/increments a build. they/we only do it incase of issues, this is of some sorts an unwritten law so to speak. devs even state it when users ask if they can do as such.