Can i wipe data after install any ROM and before reboot to OS? Tks
You can always wipe data, preferably before flashing clean, but you may flash after also.
For some pre-installed programs, you may have to flash rom again after wipe.
Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
A clean flash (wipe data, cache and Dalvik/ART - the default wipe in TWRP) is typically recommended before flashing a custom ROM. Yes, you can wipe after flashing, but I don't see a benefit if you already wiped before flashing the ROM.
redpoint73 said:
A clean flash (wipe data, cache and Dalvik/ART - the default wipe in TWRP) is typically recommended before flashing a custom ROM. Yes, you can wipe after flashing, but I don't see a benefit if you already wiped before flashing the ROM.
Click to expand...
Click to collapse
Sorry, The correctly question is: Can i wipe internal storage after Flash a ROM using twrp, and before boot to the system?
rgregor210881 said:
Can i wipe internal storage after Flash a ROM using twrp, and before boot to the system?
Click to expand...
Click to collapse
Yes
rgregor210881 said:
Sorry, The correctly question is: Can i wipe internal storage after Flash a ROM using twrp, and before boot to the system?
Click to expand...
Click to collapse
Technically yes. But if you intend to do this, there are some considerations: If you made a TWRP backup of your current ROM (which you should always do before flashing a new ROM), than that backup will be lost when you wipe internal storage. Similar thing with Titanium Backup or any other similar backup tools.
You'll also lose whatever ROM zip you are flashing. And it's not that unusual that things do go quite right with a ROM flash, and you want to flash it again.
These points can certainly be worked around, for instance with adb sideload or adb push, or mounting storage in TWRP. But it's extra steps, that should be considered. At a minimum, you should know how to (be prepared to) put a "known good" TWRP backup or ROM file back onto the phone.
Related
So every single rom for any phone I've seen says to clear the dalvik and the cache (or maybe its just the "dalvik cache") but when I went from stock to Thriller, I forgot to, and nothing went wrong. In fact, all my settings and apps were all intact from the previous stock rom.
I've considered that the only other phone I'd done any flashing on was a backflip, without Apps2SD and maybe that's why all my apps and settings were intact, so that still leaves me with the question: why clear it?
This may be a noob-ish question, and I apologize. Thanks for any help!
Tyqar said:
So every single rom for any phone I've seen says to clear the dalvik and the cache (or maybe its just the "dalvik cache") but when I went from stock to Thriller, I forgot to, and nothing went wrong. In fact, all my settings and apps were all intact from the previous stock rom.
I've considered that the only other phone I'd done any flashing on was a backflip, without Apps2SD and maybe that's why all my apps and settings were intact, so that still leaves me with the question: why clear it?
This may be a noob-ish question, and I apologize. Thanks for any help!
Click to expand...
Click to collapse
If there are any compatibility issues between the apk dalvik cache of your previous rom and the apks on the new rom wiping dalvik clears the previous apks stored dalvik cache. In most cases you can flash without a problem. But I recommend wiping between rom flashes just to eliminate any potential problems. Flashing something like Thriller over the stock rom you can probably get away with not wiping anything since all the apks are essentially the same. Flashing kernels you don't need to wipe anything. When flashing a rom with a completely different firmware I recommend a full data wipe. Restoring recovery backups such as nandroid require no wiping at all.
Also, wiping dalvik shouldn't affect any of your settings.
Sent from my LG-P920 using Tapatalk
+1
When switching ROM with different base apps, it is generally better to wipe caches than to get stuck in a boot loop, or having your apps and launcher FC on you. You never lose anything as the cache rebuilds itself on the next reboot, except maybe a few minutes
CallMeAria said:
If there are any compatibility issues between the apk dalvik cache of your previous rom and the apks on the new rom wiping dalvik clears the previous apks stored dalvik cache. In most cases you can flash without a problem. But I recommend wiping between rom flashes just to eliminate any potential problems. Flashing something like Thriller over the stock rom you can probably get away with not wiping anything since all the apks are essentially the same. Flashing kernels you don't need to wipe anything. When flashing a rom with a completely different firmware I recommend a full data wipe. Restoring recovery backups such as nandroid require no wiping at all.
Also, wiping dalvik shouldn't affect any of your settings.
Sent from my LG-P920 using Tapatalk
Click to expand...
Click to collapse
so, when i flashed thriller and followed the instructions, did I do a full wipe or not?
I mean if it doest it on its own, and if not, should I do one?
latinohot said:
so, when i flashed thriller and followed the instructions, did I do a full wipe or not?
I mean if it doest it on its own, and if not, should I do one?
Click to expand...
Click to collapse
If you followed the instructions you did a full data wipe. When you do this the dalvik gets wiped as well. To just wipe dalvik look under the Advanced menu in cwm recovery.
Sent from my LG-P920 using Tapatalk
clearing cache
i am using a nand rom in my HD2, and i also want to install another rom via SD in Magldr, but because of kernel issues i cannot load the Rom from SD unless i use the kernal i am advised to use. I am instructed to clear the dalvik and cache, but does this mean that i would lose anything from my current NAND rom? I still want to be able to use that of coarse so i just want to make sure there are no major risks when clearing cache.
ssj5legend said:
i am using a nand rom in my HD2, and i also want to install another rom via SD in Magldr, but because of kernel issues i cannot load the Rom from SD unless i use the kernal i am advised to use. I am instructed to clear the dalvik and cache, but does this mean that i would lose anything from my current NAND rom? I still want to be able to use that of coarse so i just want to make sure there are no major risks when clearing cache.
Click to expand...
Click to collapse
Clearing dalvik and cache wont make you lose anything, used to do it with my shift because I'd flash about 10 zips a day sometimes...
Also when it comes to flashing any ROM I format system data cache wipe dalvik cache and do a factory reset just to be sure nothing from a previous ROM is left over also wipe my SD ext partition when running an a2sd ROM, my question is can I safely manually format the emmc partition of the thrill from the mounts and storage option of cwm
Sent from my LG-P925 using Tapatalk
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.
Hi guys,
I believe this question has been asked multiple times, and i myself tried searching for answers from many various source to clarify my doubts, only to get more confused due to conflicting information.
Let's say now i am on a custom ROM. Before flashing the custom ROM, i made a backup of my stock touchwiz rom using cwm. However i want to revert back to the exact same state before flashing the custom ROM. What are the steps i need to do to restore the backup file?
1) Some sources mentioned just booting into cwm recovery, selecting "backup and restore" option, select "restore" and choosing the desired backup file will allow the phone to restore to the state prior to flashing.
2) Some other sources mentioned needing to wipe cache/wipe delvik cache/format system/format cache etc. first before i can restore the backup file.
So which is it?
Thank you!
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Cundis said:
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Click to expand...
Click to collapse
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
chainer22 said:
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
Click to expand...
Click to collapse
Wipe /
If problems format .
jje
Any other things i should look out for or preventive measures i should take for restoring backup from cwm?
i have been reading of cases where restoration through cwm fails and they have to go through the whole process of re-rooting and flashing before being able to restore it
there is no need for wiping, the recovery does it on its own prior to restoring.
got stuck
i erased everything followed 2nd step now its stuck on logo not starting
rishiud said:
i erased everything followed 2nd step now its stuck on logo not starting
Click to expand...
Click to collapse
Factory reset
factory reset
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
rishiud said:
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
Click to expand...
Click to collapse
Well you are in the wrong forum this is SGS3 I9305 .Not your phone ,
.......................................................................
Hi there! I want to test the official CM12.1 rom so I decided to format the phone and flash a custom kernel and then the rom.
First I flashed TWRP (2.8.7.0) using fastboot and enter it. I made a complete wipe using the advanced wipe and marking all options (except usb-otg).
Once the partitions are clean I flashed the kernel using the install option and selecting the zip file, finally the same for the CM12.1 rom (nightly). Wiped cache and dalvik and restart, but somehow miui reinstalled.... (it is possible to completely delete miui?). The kernel seems to be the stock (3.4.0-g7f72d41-01413-g70bd50e).
I read in the official CM12.1 post that the rom automatically extends the system partition (merging the two system partitions to have a partition with 1.28GB), is this true or do I have to do it manually (flashing something?).
Thanks.
Flash this once and your partition will be 1.2 GB.
Thanks! Is it normal that it still shows just 629MB? (I can see it in the repair/resize/change-file-system section).
Now, every rom that I flash it stucks at the "mi boot logo"... Maybe I'm doing something wrong; I wipe/factory reset (including cache/dalvik) and then flash the zip, and (wipe again, the option at the left to reboot) and reboot to system.... It's stuck, I tried with other custom roms and it happens the same. What am I doing wrong??
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
pratyush997 said:
Did you switched the partition (system 1 for non - miui and system 2 for miui)? It's located in advanced options in cwm.
Click to expand...
Click to collapse
I'm using TWRP. So I have to flash CWM to extend the partition?
ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
I do not use TWRP, can't help you.
ChazyTheBest said:
I'm using TWRP. So I have to flash CWM to extend the partition?
Click to expand...
Click to collapse
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
zzvilzz said:
Yes, the repartition zip only works on CWM. People said that they have problem while repartitioning with TWRP.
Click to expand...
Click to collapse
did you solve your problem?...im having that same problem of you :crying:
So, I have the nexus 6 and one plus 3t...on the 3t, going back to nougat you have to wipe internal storage, do you have to do the same here?
jamescable said:
So, I have the nexus 6 and one plus 3t...on the 3t, going back to nougat you have to wipe internal storage, do you have to do the same here?
Click to expand...
Click to collapse
If you're referring to flashing the factory image, yes I it will automatically wipe internal storage. Alternatively you could just wipe system/data/cache/dalvik and just install a nougat based custom ROM, the most recommended one being the infamous PureNexus. Some people its possible to flash the factory recovery from inside TWRP so give that a look too. :good:
Ta3miyyasandwich said:
If you're referring to flashing the factory image, yes I it will automatically wipe internal storage. Alternatively you could just wipe system/data/cache/dalvik and just install a nougat based custom ROM, the most recommended one being the infamous PureNexus. Some people its possible to flash the factory recovery from inside TWRP so give that a look too. :good:
Click to expand...
Click to collapse
What I am referring to is this, on 3t, if I am on a custom Oreo ROM, and want to go back to custom nougat, if I wipe system, dalvik,data, and cache...install a nougat ROM, it will boot but make me wipe internal memory...
I don't believe there is any reason a custom nougat ROM will trigger a wipe of user data (internal storage). Of course it's always a good idea to back up just in case [emoji6]
I know you're not talking about stock, but the only time user data is wiped automatically is by using the stock install script. The script can be modified to not flash user data. Or better, just manually fastboot flash the stock ROM excluding the user data partition. The -w flag is the wipe command.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers