Related
i posted this in the Q&A but was brought to my attention that it might need to be here.
MustacheFart10 said:
I upgraded to the latest clockworkmod 3.0.0.5 and when I switch ROMs, I notice some of my item's are still "cached". For example, I was using Evervolv and then did a wipe of data, cache, and davlik, and flashed the RC1 for CM7. GApps are not packaged with either of these ROMs but when I booted up CM7 for the first time after flashing, GApps are installed, without me doing so. Is there an issue with the latest version of deleting cache or am I not doing enough wiping?
Click to expand...
Click to collapse
Ya I agree. I notices after wiping from nightly 38 to Cm7 RC1 all my settings and SMS and so on were still there. Odd...
Sent from God, who uses CM7 RC1.
It hasn't been fully wiping for me either. I've tried the setting from within ROM Manager as well as booting into recovering and manually telling it to wipe it. I also can't seem to back 3.0.0.5 out either.
the google backup service will restore some apps if you have it enabled in settings. by default it is enabled. this may be whats happening after your wipe.
I cant explain smokeey's sms messages tho
I understand google backup services but that would imply you have GApps installed, which shouldn't be after a full wipe and flash of new rom
Sent from my ADR6300 using XDA App
also, if you haven't seen this maybe its worth trying...
http://forum.xda-developers.com/showthread.php?p=11469360&highlight=recovery#post11469360
good luck, i haven't had any issues with 3.0.0.5... yet
I've run into some issues as well. Went from Evervolv to my CM7 backup and when I restored the nandroid for CM7 the status bar was totally gone lol.
Google Apps are stored in /system/app. Wiping /data and /cache won't erase them.
With CWM, it's best to go into Mounts & Storage, and format system there. Then flash the ROM.
gmichaelow said:
Google Apps are stored in /system/app. Wiping /data and /cache won't erase them.
With CWM, it's best to go into Mounts & Storage, and format system there. Then flash the ROM.
Click to expand...
Click to collapse
That makes sense, I noticed that whenever a rom developer says that the wipe is scripted into the install or update that, that is what it does is format the mounts first.
MustacheFart10 said:
i posted this in the Q&A but was brought to my attention that it might need to be here.
Click to expand...
Click to collapse
I can't get the Warm Two Point Two rom to flash since I upgraded. Even after flashing other recoveries (2.5.1.2, and 2.5.1.8) I still have problems flashing other roms.
I went back to 2.5.1.2 from 3.0.0.5 I notice little "gliches" with the 3.0.0.5 that didnt make it worth the upgrade. on a side note. Evervolv rocks!!! lol
sgtagem said:
I went back to 2.5.1.2 from 3.0.0.5 I notice little "gliches" with the 3.0.0.5 that didnt make it worth the upgrade. on a side note. Evervolv rocks!!! lol
Click to expand...
Click to collapse
I went back too, but I wish could get rid of the update notice every time I open Rom Manager.
platodd said:
I went back too, but I wish could get rid of the update notice every time I open Rom Manager.
Click to expand...
Click to collapse
Press menu when ROM manager is open. Unchecked update notifications.
Sent from my ADR6300 using XDA App
3.0.0.5 won't even boot for me. Rom Manager reports it as installed, but until I reverted to 2.5.1.2 I couldn't even get into recovery.
cam30era said:
Press menu when ROM manager is open. Unchecked update notifications.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nice.... i guess i looked real hard there
gmichaelow said:
Google Apps are stored in /system/app. Wiping /data and /cache won't erase them.
With CWM, it's best to go into Mounts & Storage, and format system there. Then flash the ROM.
Click to expand...
Click to collapse
Do you usually do the format boot, system, data, cache, and then go and wipe data, cache, and davlik? I did the format from the mount & storage and it still kept my home screen options...
MustacheFart10 said:
Do you usually do the format boot, system, data, cache, and then go and wipe data, cache, and davlik? I did the format from the mount & storage and it still kept my home screen options...
Click to expand...
Click to collapse
Go into recovery and do a Factory Reset which will format system, cache and data.. Then install the ROM via the install zip file option and you should be good to go.
I have been having that problem also. I was running MIUI and I wiped everything as usual and flashed Liguid Metal and MIUI backup, music, and gallery were all still in my apps list. So I wiped and flashed again, but they were still there and I was unable to uninstall them.
I ended going back to an older version of CWM so i could try a few other ROMs because there are still a many that are incompatible.
Can someone please pm me with a link to where I can find an older version of CWM recovery. I am having issues as well.
Sent from my ADR6300 using XDA App
NilsP said:
Go into recovery and do a Factory Reset which will format system, cache and data.. Then install the ROM via the install zip file option and you should be good to go.
Click to expand...
Click to collapse
That's the problem is that doesn't work. I found that doing the formats in mount and storage that I listed above and then wiping data, cache, and davlik solved my issues.
Sent from my ADR6300 using XDA App
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
I had flashed Warm TwoPointThree. Didn't really like it so I restored to my nandroid back up. Now the phone randomly crashes for no apparent reason. It is sitting next to me on my desk and just now it crashed, wasn't even touching it. Secondary to the crashes is that after it happen and I try to report the phone is registering no charge and then immediately shuts down till I put it on a charger, regardless of actual battery charge.
Edit
More info. It has never crashed while on the charger. Don't know if that is relevant.
Did you wipe properly prior to restoring your nandroid? Also, what recovery are you using? If it's not Amon-ra, you need to get it! Make sure when doing a nandroid restore you have the appropriate items checked for restore (Assuming you did this when making the nandroid to begin with). Usually Boot, System, Data, and SD ext if partitioned.
Im using Amon-ra and I have an unpartitioned SD card. What do you mean by wipe? I'm a new to the entire rooting thing.
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
dieselford said:
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can I use the wipe feature in Amon-ra to do this?
Yes. That is the way to do it.
Sent from my PC36100 using xda premium
Try fix permissions, I think RA has it under other, or if u have Rom manager there is an option to fix permissions
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
SabaBoBaba said:
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
Click to expand...
Click to collapse
Yes that's it.
Well the crashes have started again. They seem to start slow, one crash then like 3 days later another and then just increase in frequency, today it crashed 5 times before noon. I'm at the point that I think perhaps I need to wipe and not attempt to do a restore. My concern is will I lose my root if I do that?
Will I lose root if I do wipe with out restoring afterward?
SabaBoBaba said:
Will I lose root if I do wipe with out restoring afterward?
Click to expand...
Click to collapse
If you wipe without restoring, you won't have a ROM on your device. You'll have to flash one, and as long as it's a custom or rooted stock ROM, you'll be fine.
Well I did a factory reset tonight so we'll see how that goes. Thanks to those people who contributed.
Well I did the factory reset and this morning it crashed again. I'm at a loss. All this started after I installed the Warm 2.3 ROM and then restored back to a backup to get the stock ROM back. Any thoughts on what to try now?
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
SabaBoBaba said:
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
Click to expand...
Click to collapse
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Captain_Throwback said:
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Click to expand...
Click to collapse
Well Im going to flash this http://forum.xda-developers.com/showthread.php?t=1455340&highlight=stock+rom and see if that works. Thanks for the assist.
After wiping last night and loading the rooted version of the latest stock ROM it crashed again today. Next idea?
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Grizraz said:
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Click to expand...
Click to collapse
Ill give that a shot. I hope I can fix what ever I did to foul this thing up.
Just from searching the forums I really dont understand this edify thing. Can you help be get some clarity on it?
Hey all,
I've been searching for a while now and decided I should just post my question finally. I have the Galaxy SIII, rooted, and running CM10 stable. For the last 3 months or so, my SMS app, Messaging, has been randomly force closing and crashing. The only way to fix it is by rebooting the phone. I've tried re-flashing the mod 5 times, and even wiped data and done 2 factory resets. Still no luck.
And more recently my "phone" app has been doing it too. It crashes when I open up the dial pad and drops calls randomly and I have to restart my phone for it to work again.
Both of these will happen randomly. Sometimes I can go 4 hours without having to restart my phone, other times I have to restart my phone every 20 minutes. It's really starting to bug me.
Is there an app that's known to cause these crashes? Or is there a possibility that the mod file is corrupt? Thoughts? Questions? Any help is appreciated!!
When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.
xBeerdroiDx said:
When you flashed Cm10, did you come from stock or a custom rom? Did you also format /system?
If you made a nandroid while on stock, I would:
Wipe data, cache, dalvik and restore that. Then (assuming you still have Cm10 and gapps zips on your device) I would wipe data and caches again, format /system and flash rom/gapps. Wipe data/cache and reboot.
Click to expand...
Click to collapse
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?
tango259 said:
When I flashed, it was from a previous CM10 ROM that worked fine. I reflashed because one of my apps was getting an "unknown" error, and now this crashing is happening. I don't think I have ever done "format /system". How do I go about that?
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one
xBeerdroiDx said:
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data
Reboot
Be sure to have whatever you feel important backed up as this will wipe your system. Make a nandroid first if you don't already have one
Click to expand...
Click to collapse
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.
tango259 said:
Thanks!! I'll try it tonight and post with the results tomorrow. Last time I flashed it took 2 days until the problems arose again.
Click to expand...
Click to collapse
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results
What the???
xBeerdroiDx said:
There shouldn't be any issues if you have flashed correctly. Many users have also noted that a custom rom performs better when returning to stock and then flashing the new rom via the above procedures. Feel free to pm me your results
Click to expand...
Click to collapse
To have a completely clean install, you should always:
Wipe data
Wipe cache
Wipe dalvik (under advanced)
Format /system (under mounts and storage)
Flash rom
Flash gapps
Wipe data <------------- ????
Reboot
I can't see this is a good thing, but I'm a noob.
You're saying after installing the new ROM and apps (Flash rom Flash gapps), you then go back into CWM and select 'wipe data/factory reset'??
Again, I'm a noob and maybe I'm reading this wrong!
Doing a wipe again right after installing a new ROM sounds so wrong to me.
What would that do?
RoidRulez said:
Wipe data <------------- ????
Click to expand...
Click to collapse
This step (step 7 in your list) isn't necessary.
When in doubt, follow the directions in the OP of the rom you are trying to flash, usually can't go wrong.
so i formated the internal storage with team win rcovery. I installed Alpha s4 v2.0 and it works fine but when i install anyothere mods and reboot my phone it stays on the logo Galaxy S 4 logo and I have to re flash the ROM again but i have to formatted the internal storage again just to flash the rom . does any one have any idea how to fix this pls help
Reformat it in recovery
Sent from my SGH-M919 using Tapatalk 2
richardlibeau said:
Reformat it in recovery
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
what do you mean like how ? because installing rom like doing a factory reset doesn't work get me on to the Galaxy S 4 logo and that it. I have to format the data just to install any Rom dont know why but im getting frustrated about it
SuperAndroidman said:
what do you mean like how ? because installing rom like doing a factory reset doesn't work get me on to the Galaxy S 4 logo and that it. I have to format the data just to install any Rom dont know why but im getting frustrated about it
Click to expand...
Click to collapse
Should be an option in mount storage or advanced section of recovery to format .
Sent from my SGH-M919 using Tapatalk 2
STOP!!! TWRP is known for messing up your phone when you format internal memory. It will lead to bootloops and even the rom not booting at all. Switch recoveries to Clockwork or Philz and you will be fine. You may need to Odin back to stock to fix the issue first.
Cal-El said:
STOP!!! TWRP is known for messing up your phone when you format internal memory. It will lead to bootloops and even the rom not booting at all. Switch recoveries to Clockwork or Philz and you will be fine. You may need to Odin back to stock to fix the issue first.
Click to expand...
Click to collapse
just doing Odin put me back stock or do i need look for the stock rom and stock kernel then run odin? link pls
What to Wipe in TWRP
If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.
http://teamw.in/whattowipe
http://teamw.in/project/twrp2