Moving from Snapshot M10 to a newer Snapshot M11, need always to reset data on CWM? or is not needed?
Lot of time to setting all again every month, Thanks in advance
I don't know the answer but have you tried updating without wiping /data? Seems like you've nothing to lose trying...
Erik FX8 said:
Moving from Snapshot M10 to a newer Snapshot M11, need always to reset data on CWM? or is not needed?
Lot of time to setting all again every month, Thanks in advance
Click to expand...
Click to collapse
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
TechnoSparks said:
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
Click to expand...
Click to collapse
I'm new to this so just wanted to confirm something if you wouldn't mind. I'm using MrSteve's CM port for LBL and he says to just flash the new ROM over the old when updating versions. I can only assume he knows best but is the above some voodoo that is recommended anyway, even if unnecessary?
Thanks.
ricodredd said:
I'm new to this so just wanted to confirm something if you wouldn't mind. I'm using MrSteve's CM port for LBL and he says to just flash the new ROM over the old when updating versions. I can only assume he knows best but is the above some voodoo that is recommended anyway, even if unnecessary?
Thanks.
Click to expand...
Click to collapse
In this case this depends on the developer. It seems that if MrSteve555 said to do so, then I believe it is best to follow his words. Well if you notice, I said it is a good practise to do those wipes.
If you don't do system wipe, a new zip will flash the new files and replace the old one. There are no disadvantages on doing this. But some ROM do recommend wiping the system first.
Above all, wipe the system as it might keep troubles away unless stated otherwise by the respected developers
Thanks, TechnoSparks. And the same goes for /cache, dalvik-cache too? I don't mind waiting the few extra minutes it takes to wipe these too if there's any benefit.
ricodredd said:
Thanks, TechnoSparks. And the same goes for /cache, dalvik-cache too? I don't mind waiting the few extra minutes it takes to wipe these too if there's any benefit.
Click to expand...
Click to collapse
Yes its optional too but widely recommended across the forums. I am not so sure about the benefits. But let's just assume that your device will be a lot fresher if those wipes are performed. And just maybe, when I will have to flash a ROM in the future, I will try to ignore the wiping of cache and dalvik-cache and see if they do some negative impacts on the ROM.
Wiping the dalvik-cache only took 0 to 2 seconds in my experience. Wiping the /cache partition only took about 4 seconds. So it doesn't take so much time to be obvious
TechnoSparks said:
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
Click to expand...
Click to collapse
Hi,
I have flash CM11 snapshot M11 from cwm recovery. Previously I was on CM11 nightly build.
Do I need to flash the boot.img after flashing the M11 snapshot?
Thanks.
xdagops said:
Hi,
I have flash CM11 snapshot M11 from cwm recovery. Previously I was on CM11 nightly build.
Do I need to flash the boot.img after flashing the M11 snapshot?
Thanks.
Click to expand...
Click to collapse
No, you don't have to flash the boot.img anymore.
Related
I received a notification from ROM Manager that CM7 Nightly 19 was available.
It seems not a good idea to use this. I believe you need to format the cache partition first? And doing this thru ROM manager seems that it would not allow for that?
Anyone use ROM Manager OTA's successfully with CM7?
it does allow you the option of wiping the "data and cache" before installing, but i'm leary of wiping the "data" part. is that all our app data?
Yeah, with the Nightlies, I believe you can flash them on top of the older version without wiping data. So I definitely do not want to do this every night!
Eddog4DROID said:
Yeah, with the Nightlies, I believe you can flash them on top of the older version without wiping data. So I definitely do not want to do this every night!
Click to expand...
Click to collapse
I flash my nightlies with out wiping.
Yes, I don't wipe the data, but I do wipe Cache Partition. Isn't that necessary? Or do you flash from Rom Manager as is without wiping data, cache, anything?
i wouldn't use rom manager to flash. use it to download and boot into recovery only.
also good for flashing latest recovery when needed.
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
Not sure about this particular case, but I'll tell you my approach is to *always* do a full wipe + format partitions and internal sdcard before flashing *any* ROM. This way I'm sure there's nothing old left (app data, config etc.). Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now), I think it's worth the time to reinstall and reconfig everything. If you don't need to keep old data and config:
1) Wipe data & cache
2) Wipe dalvik cache
3) Format /system & /preload
4) Format internal sdcard (make sure you save anything you need before)
5) Flash ROM
6) Wipe cache again
7) Wipe dalvik cache again
8) Reboot
(Not sure if 6 and 7 are needed, but I prefer to be a bit paranoid in this case.)
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
I think it depends on which custom rom u r currently on & which one you are gonna flash..for ex: flashing Ultimate v5 XXLSA over Alliance v1 XXLS7 may not work..
dbolivar said:
Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now))
Click to expand...
Click to collapse
I agree with you. If you perform a full wipe before to install a new rom, the probabilities of occur in some rom's issue (like FC or just a "simple" weird lag) are low. Tested personally.
It always better/advised to perform a full wipe.
In the end, you could do a nandroid backup of your last used rom, wipe everything, install the new rom, and then try to restore the data partition only. If you get some errors or general issue, you can easily full wipe everything again, and reinstall the new rom again... at least, you tried
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
What does the OP states? Flashing ROMs is STILL a dangerous business.
Read the OP for the ROM you are installing
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
leaks always require full wipe for it to function properly.
Received this phone a month ago, just got around to rooting it yesterday. Root with motochopper went fine. Unlocked the handset with motopocalypse, everything went fine. Installed latest CM10.2 nightly and everything ran fine, even restarted phone and it worked fine. I then realized I forgot to install Gapps, So i went to CWM and installed the Gapps through "install zip from sd card". Now phone will not progress past the bootloader unlocked warning screen. I can restart and put phone into recovery or fastboot no problem but I don't know where to go from here. I tried a factory reset and reinstallation of CM but to no success. I am a bit of a newb when it comes to external programs like RSD Lite and haven't used it. Is there something obvious I'm missing in my progress of trying to fix my phone?
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
i can't post outside links yet but on the wiki.cyanogen site in the Gapps section I used the 10.2 20130813 1f51b5cc6370c1f45dc951109b6ce6ed release. I will attempt those steps once i can find a legitimate charger in my house. Phone doesn't accept power unless its on and i need just a bit of juice to boot it up
frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
Here's the official name. Installed cm-10.2-2-130814-NIGHTLY-mb886.zip for the cm and gapps-jb-20130813-signed.zip for the GApps, both latest versions I believe
frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?
yodelyfish said:
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?
Click to expand...
Click to collapse
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up
frog1982 said:
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up
Click to expand...
Click to collapse
i got Cyanogen up and working. And no I was not flashing gaps Before first boot. i will try doing that before everything else
I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?
yodelyfish said:
I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?
Click to expand...
Click to collapse
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.
frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.[/Q]
Awesome. Pac-Rom already looks better on review. I get to the dl page tho and have a monster list of choices. Which one do I go for?
Click to expand...
Click to collapse
frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.
Click to expand...
Click to collapse
Thank you for all the help. PACROM is up and running swimmingly, all of the features are there and it is definitely better than CM by itself. Thanks again
When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
EDIT: Wiped only Dalvik and flashed the update, works smoothly and the black browser bug is fixed.
Stirlitz_the_Medved said:
When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
Click to expand...
Click to collapse
I have found clean wipes the best but use the recovery option to reload certain data etc or back up apps and reinstall clean.
Basically, i back up contacts, calendars, sms etc anyway these days. Makes for an easy transfer of data when needed.
Sent via HTC Velocity 4G + [HolicsROM v1.3] [Sweep2WAKE]
Stirlitz_the_Medved said:
When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
Click to expand...
Click to collapse
If you are updating the same ROM... Usually you don't need to wipe... Anything more than dalvik cache and cache
However... EVERYONE will ask you and then suggest a full wipe if you have any issues...
Sent from my Vivid 4G using Tapatalk
Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.