I always see in rom threads about FC issues and other problems. I never had any of those problems and i've flashed roms countless numbers of times. Ive never even done a fix permissions.
In most of the Rom threads it says
-Do a Wipe and Factory reset in recovery 3 times or w/e.
My way of doing things and not having any issues is-
-Wipe/Factory reset in recovey
-go to mounts and storage and format /system
-go to advanced and wipe dalvik cache
-Wipe/Factory reset once more
-Flash rom and enjoy having no issues.
3 times was suggested. Because our cwm was not made for us. So u can be certin its fully wiping. And yes good idea wipe data cache and dalvik. And format system alot of rom threads suggest this
I've found formating cache, system and data partitions, flashing darkside and then flashing rom is enough for me
icenight89 said:
I've found formating cache, system and data partitions, flashing darkside and then flashing rom is enough for me
Click to expand...
Click to collapse
Exactly what I do.......No issues at all..........
Good, I just posted this for anyone having those f/c issues and such or noobs
Well those force close issues can get to the point where even after odin of stock tar still didnt
Solve. It was weird glad no one has had them forawhile
Weird, I never had them at all. Maybe I'm just more cautious than most of the noobs we get lol
Not really a caution type thing. Eventually it will happen if just using 989 cwm wipe. Using tdj's full wipe script and 727 specific recovery is the way to go. Even fix permissions works in recovery now for me at least.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
fix permissions works for me now and I'm still usinf 5.0.2.7, so not to sure on that
Darkside is the bomb.. never had any issues since using it.
Related
Sorry, this might be kind of a noob question, but i see build 23 is out for CM7. If i flash the new build, do i need to totally set up my phone all over again?
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Genocaust said:
My last experience with CM ROMS on my G1 was that if you are upgrading to a new CM version a wipe is recommended but not necessary. However, if you do not wipe and experience problems it will be the first troubleshooting step suggested to you
YMMV on the MT4G builds, but that's how it worked with the G1
Click to expand...
Click to collapse
Thanks. Ugh, i didn't even think about that when i flashed CM7. Seems like it is a real PITA to wipe every time and have to configure all the settings again.
I had good success on my move from stock -> Ice Glacier (un-crapwared stock) by making a full TitaniumBackup of -everything- and then restoring it app by app (along with settings). They are similarly built ROMs, and it worked well for me with minimal downtime. You may want to consider trying that if you are just changing between CM flavors, as I would presume they are mostly backward compatible with a few fixes/features here and there. At worst it may leave you with just system settings to redo.
When i flash a new CMNightly all i do is wipe the cache and the Dalv/Cache and i've yet to have any problems. If you are worried about wiping and restoring everything. you might want to look into Titanium Backup.
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
shortskoolbus said:
thanks. I flashed without wiping and it seems to be fine. I was worried more about my system settings than apps.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Wiping the Cache and wiping the Dalv Cache will not reset the phone. Only a full wipe will do that.
To my understanding, a "full wipe/factory reset" in Clockwork Recovery will only clear /cache, /data, and Davlik cache. /boot and /system will not be touched. Some users moving from Froyo to Gingerbread have had problems with /system, and a wipe of /system (from within Clockwork Recovery or from adb) has solved some problems for people, beyond what a full wipe can do. Discussions are in the CM7 thread in the Application Development subforum.
I know, most people refuse to search for anything.
i usually wipe the Cache and the Dalv Cache when updating nightlies, but several times i've wiped nothing and just flashed the new one on top and its always worked just fine for me
I always do a full wipe when installing roms. Setting it up each time makes me think its a whole new phone which is cool.
You do NOT need to wipe when upgrading to a new version of the same ROM. I've probably flashed 10 no-wipe updates of cm7 on my phone and it's still perfectly stable, no force closes or anything.
Boot into recovery and wipe cache and dalvik cache before flashing. Give it a few mins to "settle" on the first boot, reboot again and you're good to go.
Worst-case scenario you'll just wipe and reflash anyway, and nothing lost.
.. that does the equivalent task29 we used to do in WM6.5 ?
What task 29 used to do, is wipe the whole device, rendering it non-bootable.
So everytime you wrote a new rom on it, it had fresh system files on it.
Is that possible on android, or is it not needed ?
I mean wipe data/wipe cache/wipe dalvin on cwm is enough to wipe the system clean ?
#1 wrong section
#2 do
- factory reset
- wipe cache
- wipe dalvik cache
#3 do #2 3 times
Device is clean!
RinTinTigger said:
#1 wrong section
#2 do
- factory reset
- wipe cache
- wipe dalvik cache
#3 do #2 3 times
Device is clean!
Click to expand...
Click to collapse
Why would you do #2 3 times ?
Why is this the wrong section ? I asked the dev's.
Questions belong to Q&A
i learned the hard way
We do #2 multiple times, cuz cwm and amon_ra showed that some times for some roms, on wipe isnt enuf
You don't need to make the phone unbootable; it's not necessary to do that to flash a new rom.
The clockwork wipe/factory reset should be good enough for any phone. That also wipes the cache and dalvik-cache anyways, so the other steps are just being a bit anal, but don't do harm, and some do think they're necessary. (FYI - I do them too. LOL).
IF you ever want to TOTALLY wipe the phone, including all personal data, apps, and sdcard contents, the quickest and easiest way appears to be just run the fastboot oem unlock command on the phone again. Total wipe of everything outside the /system partition.
There is something like a task29. The only place I know I exist is for the G1. It is called superwipe and is flashed from recovery.
It wont work with the nexus s?
Sent from my Nexus S using XDA App
distortedloop said:
You don't need to make the phone unbootable; it's not necessary to do that to flash a new rom.
The clockwork wipe/factory reset should be good enough for any phone. That also wipes the cache and dalvik-cache anyways, so the other steps are just being a bit anal, but don't do harm, and some do think they're necessary. (FYI - I do them too. LOL).
IF you ever want to TOTALLY wipe the phone, including all personal data, apps, and sdcard contents, the quickest and easiest way appears to be just run the fastboot oem unlock command on the phone again. Total wipe of everything outside the /system partition.
Click to expand...
Click to collapse
Hm i didnt think of that. Last night i did a format of my sdcard and a odin restore into 2.3.1. I had weird behaviour before with all the nightlies and the different kernels and stuff and after 3-5 wipes of cwm i would still find trash in my phone. Everything works fine now after all that hassle, but i loved the task29 back in the days. Heck i got my hd2 out of the drawer just to task29 it.
Sent from my Nexus S using XDA App
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
I have been trying the new ICS ROMS and have an interesting observation to share. I have had many weird problems like the shutdown reboot issue, touch key lights staying on, force closes etc. The only time I had a clean install (without even the shutdown issue) was when I first used CWM to wipe everything and then used the stock (gingerbread) 3e recovery to perform another wipe before flashing a ROM. Anyone willing to try and confirm?
when u say another wipe using stock recovery, u mean just a factory reset, before reflashing cwm and then ics? becuz if so, ive tried that, and it was still hit and miss
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
rushi.1986 said:
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
Click to expand...
Click to collapse
It seems like there isn't an easy fix that works for everyone (for the shutdown freeze bug anyways--this was the one problem I just couldn't get rid of until just a couple days ago). I had a theory that Darkside superwipe was screwing it up for me (the method you use as I've quoted was basically my method for wiping prior to flashing any roms, with the exception of using 3e recovery).
Seanzscreams new Sky ICS rom claims to have fixed the shutdown issue for good. I don't know if this is true for everyone but it seems to have worked for me.
What I do is:
Flash darkside x1
factory reset x5
wipe cache x5
wipe dalvik x5
format system x5
Flash radio
wait 1 minute
flash rom
wait 1 minute
reboot and don't touch phone for at least 10 minutes
I've noticed that some people go to the extreme when it comes to wiping....... Super extreme.
I've always in my YEARS of flashing roms (I got G1 on day one), I've always done just a simple format of data and cache. Normally don't get any unexplained errors or bad flashes.
LOT of the problems rise from users. Either installing something that is buggy or just not following directions.
Restoring backups is probably the BIGGEST CULPRIT OF ALL. Often times, people just restore files that they shouldn't. Adding themes, adding animations, boot animations blah blah blah...then blaming devs because so and so is not working.
I use restore but I'm selective about my restores. I don't just restore everything that I just backed up. Has NEVER caused me any problems.
Does anyone have a zip that will wipe my phone clean so that I can install a new ROM? I have one for my GS3, but I was unable to find one for my One X. Even with a Google search.
Kelton Rivas said:
Does anyone have a zip that will wipe my phone clean so that I can install a new ROM? I have one for my GS3, but I was unable to find one for my One X. Even with a Google search.
Click to expand...
Click to collapse
You'll need to find the RUU for the firmware that your phone is currently on. Download the ruu to your computer. Plug in phone and boot into fastboot. Run the ruu on the computer and it will bring your phone back to 100% factory status.
It won't wipe your sdcard though. To get it squeeky clean, you'll need to format the sdcard.
Sent from my HTC One XL using Tapatalk 2
I think he's talking more along the lines of caulkins format all zip.
Try searching for that. It formats system, data and cache.
Sent from my HTC One X using xda premium
To be clear, you don't "need" any such zip in order to install a custom ROM. Some people believe such "Superwipe" zips are a cleaner way of doing it (and may also be useful if you are experiencing bugs after a ROM flash). But I've never used anything of the sort, and never had any issues.
Just wipe cache and Dalvik, then factory reset in recovery (do not factory reset in bootloader, as this corrupts the SD). Then flash the ROM. No need to format system, as this is done automatically when you flash the ROM.
By that logic, no need to wipe cache or dalvik either since factory reset does that. I find wiping system provides peace of mind and one thing to cross off when troubleshooting buggyness within a Rom.
Sent from my HTC One X using xda app-developers app
Yeah plus I'm sure I've seen ROMs that don't wipe system during the install script. I always wipe system, for peace of mind, seeing as it only takes a second.
Sent from my HTC One XL using xda premium
exad said:
By that logic, no need to wipe cache or dalvik either since factory reset does that.
Click to expand...
Click to collapse
Not sure, but I don't think that is true. I thought all factory reset did was format the /data partition (delete user data).
Also, wiping cache and Dalvik is completely harmless. They will just rebuild themselves when you reboot. There is literally no reason not to wipe them, in any number of circumstances. Wiping system . . . not so much.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
timmaaa said:
Yeah plus I'm sure I've seen ROMs that don't wipe system during the install script.
Click to expand...
Click to collapse
I've seen this on another device, but haven't seen or heard of it on this device. Although, of course I haven't flashed every ROM available.
Sure, it typically doesn't hurt to do wipe system. Although I've seen the all-too-common instance of the n00b randomly wiping things (including system) and then asking "why won't the phone boot" (umm. . .because you wiped the OS). Thus, I normally refrain for recommending to wipe system (at least without making it clear what that actually does).
In any case, my main point is that all the required wipes are available in recovery, and no special wipe "zip" is explicitly needed (although might help in certain instances, as I've already mentioned).
Isn't dalvik kept in /cache or /data?
redpoint73 said:
Not sure, but I don't think that is true. I thought all factory reset did was format the /data partition (delete user data).
Also, wiping cache and Dalvik is completely harmless. They will just rebuild themselves when you reboot. There is literally no reason not to wipe them, in any number of circumstances. Wiping system . . . not so much.
Click to expand...
Click to collapse
I'll be honest, I did use one for a while back when I used twrp. While it is kinda pointless, it is a lot faster adding it to the zip install list than going through every wipe/format option.
OT: I feel like I'm the only one using philz touch recovery. Anyone else using it? It's got a lot of nifty features.
jacobas92 said:
Isn't dalvik kept in /cache or /data?
Click to expand...
Click to collapse
I had to look it up, but apparently it is on /data. So Factory Reset should in fact wipe it.
I've probably always though of Dalvik as something that should be wiped separately, since you should (at a minimum) wipe cache and Dalvik when doing a "dirty flash". Than I just do it by habit when doing a "clean" flash.
As I already mentioned, most of us will likely agree that there is no harm in wiping things that are going to be wiped anyways "just in case".
As long as you aren't one of these folks that wipes /system, then asks why his OS is gone.