I am sure this is a stupid question, but I've looked and not found a definitive answer so I'll try here.
I have a LG G2 (AT&T) which I have rooted/clockwork/CM11. I did most of it when I had a failed OTA send me into a bootloop. (I had rooted the stock and removed some bloat which it didn't care for). I love CM11 however, there are some issues with the M5 build that I think are solved in the nightlies.
My questions are as follows:
(1) If I start flashing nightlies am I going to loose everything on my phone?
(1a) If so? How do people handle nightly flashes and always having a phone that needs setup?
(1b) If not, how do I flash the CM rom? I assume through recovery like I did before.
(2) Is there an easier way to backup and restore my setup to my phone?
(2a) I have titanium backup, and I have backed up all system and apps. However, I am not sure if restoring that will mess things up after flashing.
So basically, I'm looking to find out how people use the nightly builds and still have a mostly functioning phone on a day to day basis?
Thank you!
Before flashing a nightly for the first time:
You will need to wipe cache, dalvik cache, and data (user data--not internal storage).
Updating to the newest nightly:
You will only need to wipe cache and dalvik before flashing the new nightly. You will not lose your setup or apps. CM has its own OTA app that will automatically install new nightlies via your custom recovery (CWM or TWRP)
Jayriff said:
Before flashing a nightly for the first time:
You will need to wipe cache, dalvik cache, and data (user data--not internal storage).
Updating to the newest nightly:
You will only need to wipe cache and dalvik before flashing the new nightly. You will not lose your setup or apps. CM has its own OTA app that will automatically install new nightlies via your custom recovery (CWM or TWRP)
Click to expand...
Click to collapse
Thanks! I'm new to CM, and the thought of wiping my phone every evening was kind of scary.
bstripp said:
Thanks! I'm new to CM, and the thought of wiping my phone every evening was kind of scary.
Click to expand...
Click to collapse
Yeah once you're on nightlies, it's not a big deal. But after your FIRST flash of the nightlie, also be sure to flash the correct GApps package, which includes apps like the Google Play Store.
Related
when updating a firmware?I usually wipe all the 4 options and end up losing all my apps and SMS and stuff.
So, are all 4 wipe options to be performed?and is it normal that i have to reinstall apps each time CM is updated?
If i am not mistaken you do not have to wipe from CM rom to CM rom as of 4.1.99.
mikesm1234 said:
If i am not mistaken you do not have to wipe from CM rom to CM rom as of 4.1.99.
Click to expand...
Click to collapse
Correct, as long as that's what Cyanogen states in his directions. Occasionally devs will release a ROM that makes very significant changes that do require a wipe.
That being said... OP, all you need to wipe is the system itself. You'd only need to wipe an ext partition prior to flashing a new ROM if you had Apps2SD AND the dev recommends a wipe of system.
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
thanks!
hoopsdavis said:
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
Click to expand...
Click to collapse
Battery stats eh? cool didnt know that one! Thanks man! Going to rock this now.
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
nice.
okantomi said:
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
Click to expand...
Click to collapse
Thanks everyone for the help rocking EOS!
lol i just wish you didnt have to wipe everything....
lucky
alex94kumar said:
lol i just wish you didnt have to wipe everything....
Click to expand...
Click to collapse
I was lucky and hadn't put too much on it. So the wipe wasn't a big deal, if I'm right don't have to wipe every time to update build so was worth it. As a lot say my Xoom a lot snappier now. Would recommend doing it!
Wiping is usually the best way to go. There are workarounds, but the effort it takes to do so kinda outweighs the result.
so my question is....
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
TheLostXoom said:
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
Click to expand...
Click to collapse
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
bacon612 said:
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
TheLostXoom said:
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
Click to expand...
Click to collapse
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
okantomi said:
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
Click to expand...
Click to collapse
When first flashing a nightly a nandroid backup is recommended but it's not that necessary when going from your first nightly to another nightly. At least I don't do that because I'd rather hasten the whole data wipe/flash process and it works for me.
Disclaimer: I'm used to my old Evo 4G and use a triple wipe script built into my recovery (smelkus) whenever I flash a rom. It pretty much wipes everything.
For the Nexus 7, what needs to be wiped to flash a rom? I did a factory reset, wiped data, wiped cache, wiped system, wiped dalvik-cache, and then flashed a new rom, but I wasn't sure if all that was necessary. I'm using the latest TWRP recovery.
If I'm moving from one rom based on a jelly bean version to another based on the same version, am I ok?
Can I assume upgrading to a new version of the same rom that I don't have to wipe? (I know this one is rom specific, but in general.)
Can I leave data and will that retain my apps? Otherwise, I use Titanium Backup religiously on my Evo and now on my Nexus 7.
I searched within some of the rom instructions as well as the rooting guides, but didn't see anything specific as to what to wipe. Some threads seem to say just factory reset and maybe dalvik-cache.
Instructions with what to wipe usually come in the original post of each ROM. Usually the same ROM with different version only requires a cache wipe while moving between different ROM's requires a full wipe/reset + dalvik.
Worse comes to worse you try something and it doesn't boot and you get back into recovery and fix it.
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
gfreh said:
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
Click to expand...
Click to collapse
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
krushnam said:
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
Click to expand...
Click to collapse
Hi! Thanks for the reply, and sorry for my English.
Actually, I have already installed CM7 and it worked fine, except for the Market app. Trying to solve this, I have done a factory reset from stock recovery and, since that, CM7 is locked to the boot screen.
And yes, I have installed CM7 through CWM recovery, and I'm using a MB525 Defy.
Well, I have just tried wiping Dalvik Cache, but it seem as if nothing happens when I select this.
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
krushnam said:
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
Click to expand...
Click to collapse
How can I wipe market data? It is not an option from CWM...
gfreh said:
How can I wipe market data? It is not an option from CWM...
Click to expand...
Click to collapse
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
thiagoelg said:
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
Click to expand...
Click to collapse
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
gfreh said:
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
Click to expand...
Click to collapse
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
krushnam said:
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
Click to expand...
Click to collapse
Hi,
I have just reflashed a retailer version using RSD on a friend's computer and it is now back to life... now I'm figuring out what is the best path to follow.
Thanks for the help!
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
sa3e1 said:
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
Click to expand...
Click to collapse
Yeah... I know that. I just wanted to rollback everything and have the phone back. I'm now studying which is the best ROM for me to install again, but meanwhile, I have my phone working.
This is my first android phone and therefore cm10.1 is the first ROM I've ever had so I've never updated my ROM before. Goo manager sent me a notification saying that Cm10.1 rc2 is now available but in order to download it do I have to wipe my phone to factory default or can I just install it over my old cm10.1 and keep my apps and stuff?? Thanks
michaelsp9 said:
This is my first android phone and therefore cm10.1 is the first ROM I've ever had so I've never updated my ROM before. Goo manager sent me a notification saying that Cm10.1 rc2 is now available but in order to download it do I have to wipe my phone to factory default or can I just install it over my old cm10.1 and keep my apps and stuff?? Thanks
Click to expand...
Click to collapse
The whole point of the CM updater is that you don't have to wipe anything - not data, not cache. Just start the download, click OK to install when it finishes downloading, and it'll flash itself over your previous installation. The same applies to downgrading to an earlier release - no wipe needed.
Yes, you can keep your apps and system settings. No need to backup and restore - they'll be exactly the way they were before you downloaded the update.
However, if you are migrating to an entirely different ROM (i.e. not the official CM), then yes, you probably need to wipe. Going back and forth between different updates of the same ROM doesn't need wiping though.
You can just flash it normally using CWM. It's called Dirty Flashing. DO clear Cache and Dalvik before flashing
sigma392 said:
You can just flash it normally using CWM. It's called Dirty Flashing. DO clear Cache and Dalvik before flashing
Click to expand...
Click to collapse
So what do I do just download the ROM and its gapps again and flash them both? Which one first?
michaelsp9 said:
So what do I do just download the ROM and its gapps again and flash them both? Which one first?
Click to expand...
Click to collapse
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
sigma392 said:
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
Click to expand...
Click to collapse
No need to flash Gapps again on CM, unless data is wiped because of the b/u scripts.
The updater script in the ROM also wipes the Dalvik for you.
sigma392 said:
Wipe Cache and Dalvik -> Flash ROM -> Flash GApps -> Reboot.
And don't forget custom kernels
Click to expand...
Click to collapse
Actually you don't have to do any of that except flash the rom and reboot. All the rest is automatic.
I reverted to my backup that I made before flashing. Franco kernel didn't work and I had all the crappy apps I uninstalled from cm10.1 like Apollo and stuff .. What's new is rc2 anyways?
updating cm10.1
Hi all
I am currently using cmw6.0.2.3 and rom cm10.1.20130411-EXPERIMENTAL-p3100-M3 and would like to switch to using cm10.1 nightly. Reason to switch is because pie control in M3 is not working and I saw in some video that it is working in nightly. May i know how to update usingmanual mode please? And also will it deketenall my installed apps and data?
Thanking you all in advance
People,
1) Nandroid Backup.
2) Dirty Flash, if something doesn't work or it starts to fails, restore nandroid, backup everything (needed) with Titanium backup or similar, wipe everything, flash, restore, win.