Hey guys, I've been having a ton of problems with my note 2 freezing and restarting lately, and while trying to figure stuff out, I found out that my /data/data folder isn't being wiped! This is through a dozens of ODINs, full wipes, factory resets, etc. I've used multiple versions of TWRP as well as Philz Advanced CWM Recovery
Any way to actually get it to wipe?
How do you know that data/data isn't being wiped? It looks like you've done everything that I would suggest. Backup anything you want to save on internal storage and then wipe it as well. I like to use TWRP 2.6.3.1 for wiping internal storage and other full data wipes. it seems to work better. I then reflash Phil's recovery 6.07.9 and continue per usual with the usual wiping processes. Make sure your modem matches your rom/kernel. JellyBean+ roms need the MK4 modem. I don't have any other suggestions but you should be fine after doing full wipes with TWRP... especially the full factory dat wipe in TWRP.
Related
This is a Noob question, if I wipe data and cache 3 times with CWM and then restore a backup created just before with CWM doesn't it put back all the stuff that I tried to wipe for clean ROM flashing? Or is there garbage in there that does not get backed up and restored?
Thanks.
It will put pretty much everything back. It doesn't backup and restore the kernel, though.
So what is the purpose of wiping 3 times. Does that allow the new ROM kernel to install properly? Then we can restore everything back on top of the new kernel? The main reason I ask is after flashing a new ROM and only wiping once (I know!) about once every other day my txt messages get stuck sending. I have to reboot to send and then the clock starts again until this reoccurs. So is it best to backup with CWM, wipe 3 times, flash, then restore with CWM?
Thanks.
Wiping three times is because there has been a question about whether clockwork 2.5.x wipes certain partitions properly. Apparently it returns back from the function much faster than it should. Some people do seem to have intermittent problems when wiping once. I generally only wipe once between roms, but if anything isn't working right I go back and wipe 3x and reinstall.
Generally, when you wipe something, you aren't going to be restoring it all back. You want to wipe between different roms because certain things may be set up differently in the two and you may get weird glitches and force closes. If you are wiping to get rid of a bug, then you shouldn't restore a buggy backup or you will probably still have the bug.
You can try doing a reinstall of the base rom, wiping first of course. Then you can go restore->advanced restore->restore data to get apps and settings back. See if you still have the problem. If so, then you're going to have to wipe again and reinstall the base rom, but DONT restore your backup. You may be able to carry some apps and settings across with something like Titanium if you absolutely can't start from scratch again.
AH! Now I get it...thank you for that explanation. Tried the 3X wipe today with restore from CWM 2.5.1 so will wait and see if the SMS problem shows up again. Thank you again.
I noticed in TWRP 2.5 that there is the option to backup/restore 'Preload'. I have also read that the ROMs based on TMo 4.1.2 need preload working properly to boot, unlike previous ROMs. Should that option to include it be checked when backing up and restoring the stock 4.1.2-based ROMs?
I've also noticed that the the Preload size is 0 when backing up other roms in TWRP, so I haven't concerned myself with it. Before TWRP 2.5, I knew nothing of preload (I guess I still don't really know anything). Any thoughts?
Well, I guess I'll find out what to do by trial (and error?). I backed up JMT JB3 (including preload) to flash the Koodo update and run it for a while. I'll restore it later on and see how it boots.
I'm not sure how it works. I'm on JMT3 myself right now. I used ODIN to update to the official release when it came out, and it was doing fine, but I wanted to try some of the custom ROMs out there that are based on it. I was rooted with CWM, and did the usual backup that has worked since I can remember. I don't remember what ROM I tried next, but I didn't like it much, so I restored my back up. It restored correctly, or so I thought. After some use I started getting FC here and there. I couldn't fix it, so I did a factory reset from within the phones settings, not through recovery. As soon as it tried to reboot I kept getting a boot loop. I never was able to get it booted. I was able to boot to recovery, flash cache and wipe scripts that were recommended, and flashed JMT3. All is good now. I know trying a cache wipe or factory reset through CWM won't work since I tried it before, so I didn't even try it for this one.
So long story short I don't know how CWM (or any recovery) handles the preload. All I know is the scripts work to flash clean, or wipe cache/dalvik/fix perms, but I haven't gotten them to work after restoring a back up. My thinking is to be careful until someone figures it out because I don't think backing up will help if I ever need to. I'll have to start fresh each time I want to flash anything.
Here are the scripts I'm talking about: http://forum.xda-developers.com/showthread.php?t=2235141
Thanks for sharing your experience. I have those same scripts handy - had to use them when I flashed JMT3.
If or when I restore, I figure I'll wipe my current preload and restore the preload in my JMT backup, then flash the Infamous cache wipe script (or equivalent function in recovery if TWRP develops something similar). I'll post again to share my results when the time comes.
I ended up wanting to restore old stock 4.0.4 in TWRP 2.5.0.0 recovery. Part of me wanted to do it just so I could test the backup/restore of the preload.
I first backed up my current rom (stock Koodo/Telus 4.1.2) with the cache and preload included. I then wiped data, system, caches and preload, and ran the restore of my old backup. The 4.0.4 booted just fine. Once I was done checking for the info that I wanted, I went back to recovery and wiped all the same stuff (everything except internal and external SD) under advanced wipe options. I then restored my stock Koodo/Telus 4.1.2 backup. It seems to be running fine now although I haven't experimented much to test for any FCs. It didn't seem to have any issues booting at least.
I may have been doing some excessive wiping - I assume restoring a partition also formats it before overwriting it. I'm not even sure I needed to wipe anything to restore 4.0.4, but I didn't want a preload (110 mb) causing issues in a rom that doesn't need it at all. In any case, I know what can be done to avoid issues restoring stock 4.1.2, although I'm still not sure what needs to be done to avoid issues.
You did it exactly right. When using a 4.1.2 Samsung rom, be it custom or stock, and backing up or restoring; the preload folder is just as important as data or system. Basically the point of the preload patition is to get the system partition to fit. By symlinking the apps from preload to system Samsung has saved room and allowed a bigger rom to work on our hardware.
As an example, I am on TWRP 2.4.? and cannot backup preload. When I tried a different rom, then went back to my backup I had FCs like crazy. Because I had used the Infamous wipe script it had wiped the preload folder but there was nothing to restore to it from my backup. I had to reflash the rom I was using (really I just wanted the preload folder installed) and then restore my backup to get it working.
I hope all this makes sense. I'm going to Twrp 2.5 so I can backup my preload folder (when I stop being lazy).
Thanks guys.
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
I have a galaxy s3 SPH-L710 from Virgin mobile and have flashed a Cyanogen mod nightly(cm-11-20140916-SNAPSHOT-M10-d2lte.decryptedKLR_) by installing its zip after wiping data,cache through CWM recovery i had no connection whatsoever so I restored my backup and gave it another try to no avail. I have tried this several times with different Roms but I have had the same problem. Now I am unable to restore my backup, and my system file now has very little space left in it. I assume I'm doing something wrong in my flashing, and need delete some of my previous flashes, but i don't know either of these, any hep would be wonderful, I'm at the end of my patience and am nearly ready to just scrap it.
Thank you for anything you can do
Instead of restoring from a backup, have you tried to do a full restore from a full wipe tar?
If you know how to use Odin, download this HERE and update PRL and Profile
sparthens said:
I have a galaxy s3 SPH-L710 from Virgin mobile and have flashed a Cyanogen mod nightly(cm-11-20140916-SNAPSHOT-M10-d2lte.decryptedKLR_) by installing its zip after wiping data,cache through CWM recovery i had no connection whatsoever so I restored my backup and gave it another try to no avail. I have tried this several times with different Roms but I have had the same problem. Now I am unable to restore my backup, and my system file now has very little space left in it. I assume I'm doing something wrong in my flashing, and need delete some of my previous flashes, but i don't know either of these, any hep would be wonderful, I'm at the end of my patience and am nearly ready to just scrap it.
Thank you for anything you can do
Click to expand...
Click to collapse
Not sure if cwm can do this (I use twrp), but every time I flash a new ROM I wipe system, cache, and data, not just data and cache.
It has been a long time since I have installed roms and when I did in the past my HTC incredible had a sd card so it was easy to get data on/off the device.
I have noticed that several ROM installs for the HTC One m7 require a full wipe which would wipe my restore backups as well. But I wanted to maintain my TWRP backup so I can revert if the ROM doesn't work or if I don't like it's features.
Can I maintain the backup and install or do I have to full wipe ?
Can I pull the backup off and then put it back on. I am sure I could get it off but once I have a bad install not sure how I could put it back on the device.
I have S-Off and Unlocked Bootloader on Verizon device.
rgps said:
It has been a long time since I have installed roms and when I did in the past my HTC incredible had a sd card so it was easy to get data on/off the device.
I have noticed that several ROM installs for the HTC One m7 require a full wipe which would wipe my restore backups as well. But I wanted to maintain my TWRP backup so I can revert if the ROM doesn't work or if I don't like it's features.
Can I maintain the backup and install or do I have to full wipe ?
Can I pull the backup off and then put it back on. I am sure I could get it off but once I have a bad install not sure how I could put it back on the device.
I have S-Off and Unlocked Bootloader on Verizon device.
Click to expand...
Click to collapse
Full wipe means BOOT, CACHE, DALVIK CACHE, DATA, & SYSTEM....
NOT INTERNAL STORAGE! NO rom install requires wiping internal storage, as THAT'S where all your TWRP BACKUPS, pics, videos, Roms, etc. Are all stored on your devicw.
So in a nutshell, NEVER WIPE INTERNAL STORAGE. IT ISN'T NEEDED FOR ANY ROM INSTALL
bdizzle1686 said:
Full wipe means BOOT, CACHE, DALVIK CACHE, DATA, & SYSTEM....
NOT INTERNAL STORAGE! NO rom install requires wiping internal storage, as THAT'S where all your TWRP BACKUPS, pics, videos, Roms, etc. Are all stored on your devicw.
So in a nutshell, NEVER WIPE INTERNAL STORAGE. IT ISN'T NEEDED FOR ANY ROM INSTALL
Click to expand...
Click to collapse
OK Thanks that makes more sense. Some instructions say to do exactly that "Wipe Cache,dalvik,data,system" and some say "Must perform Full Wipe" and the later was making me think I needed to wipe the whole device.