can someone make some wipe.zips
so we don't have to do factory reset so when can keep internal storage intact
while chasing roms
Karl said:
can someone make some wipe.zips
so we don't have to do factory reset so when can keep internal storage intact
while chasing roms
Click to expand...
Click to collapse
Wipe data from cwm
I remember using VR Superwipe on my last phone. I would flash it just before I flashed a new Rom. Would it have any use for us on our SGS3?
I'm sure Scott will port some that he made for the rezound. Just give him time.
Sent from my SCH-I535 using xda premium
droidstyle said:
Wipe data from cwm
Click to expand...
Click to collapse
its alot easy to flash a zip to wipe cache and data and system all at once
Karl said:
its alot easy to flash a zip to wipe cache and data and system all at once
Click to expand...
Click to collapse
You realize a factory reset in CWM wipes the data and cache right? After that you just proceed to install the rom, why do you need a zip?
Neverendingxsin said:
You realize a factory reset in CWM wipes the data and cache right? After that you just proceed to install the rom, why do you need a zip?
Click to expand...
Click to collapse
I use TWRP and I'm sure it wipes internal too
Sent from my Galaxy S III using Forum Runner
So good
Neverendingxsin said:
You realize a factory reset in CWM wipes the data and cache right? After that you just proceed to install the rom, why do you need a zip?
Click to expand...
Click to collapse
Exactly why I posted what I did....
so use recovery to wipe with 4 actions
or use zip and wipe with 1 action
every other device has wipe.zips why not the S3
and not the be a **** this was a request thread not a tell me why its a stupid idea thread or hey you can wipe using recovery blah blah
why its so hard for some of you to keep stuff on topic, will never know
Karl said:
so use recovery to wipe with 4 actions
or use zip and wipe with 1 action
every other device has wipe.zips why not the S3
and not the be a **** this was a request thread not a tell me why its a stupid idea thread or hey you can wipe using recovery blah blah
why its so hard for some of you to keep stuff on topic, will never know
Click to expand...
Click to collapse
Using the "date wipe/factory reset" option wipes everything in /data (this includes dalvik cache) and /cache. Then when you flash a Rom it will format /boot and /system.
I'm just trying to understand why there needs to be a zip for it or what benefits that would possibly have? I can use recovery and wipe data/factory reset with 2 finger touches on my phone, and then use a few more (depending on where you store your rom zips) to install the rom of my choice that will format /boot and /system. Even if you use a zip to wipe, you'll still have to install a rom, and it sounds like the zip method would require more actions.
I'm not trying to be a ****, just trying to understand because i've never used a zip to do my wiping. It was never taken off topic by me.
does data wipe/factory on CWM wipe internal storage
Karl said:
does data wipe/factory on CWM wipe internal storage
Click to expand...
Click to collapse
Nope. Anything on the internel sd card is safe as far as i know. I've never lost anything on it when wiping my data, and ive done that quite a lot.
http://forum.xda-developers.com/showthread.php?t=1832326
Sent from my SCH-I535 using Tapatalk 2
ok, all i can say really is that i have become a accustomed to using them
with every fone ive had
evo,evo 3d,sensation, touch epic 4g,nexus s,nexus
spydersilk said:
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
you test on our S3?
I just downloaded it about an hour ago, so no, I haven't
Sent from my SCH-I535 using Tapatalk 2
thanks for the find :good:
its makes flashing easy for us fat lazy people
No wonder there's an increase in bricks....
PJnc284 said:
No wonder there's an increase in bricks....
Click to expand...
Click to collapse
do tell
Related
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Not needed if you use a sacrificial lamb and do the aztec dance...
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1365158
Super wipe is overkill and not needed . Most recoverys work great to wipe and flash any rom fine.
-XDA MODERATOR-
ac17 said:
Hey - has anyone tried using SUPERWIPE on NEXUS S?
eg http://forum.xda-developers.com/showthread.php?t=1477955
I have been having some problems with CWM not always wiping properly, and then me getting FCs and laggy responsiveness after installing well-rated ROMs.
Superwipe is said to do a better job, but does not seem to be for the NEXUS S per se, which is why I ask.
Click to expand...
Click to collapse
Wiping storage ain't like wiping your ass, 1 wipe suffices.
Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?
Oh, one final question - have you guys ever in CWM hit 'format sdcard' to fine that once you boot up and browse your SD card the format didn't work?
Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same here.......
10....0011....10101
ac17 said:
Cool! - Thanks for the wipe all info.
It seems that I have never wiped 'Boot' in CWM and i have gone through countless custom ROMS by different makers.
Maybe that's the problem (I normally just do 'factory reset' and 'wipe Dalvik')
Is it true that if you wipe 'boot' in CWM (or if using the full wipe all script), that you need to have already put your new ROM on your SD card because you MUST follow a wipe of 'boot' straight away with an install of a new ROM, else you will brick your phone?
Click to expand...
Click to collapse
My ROMs have never been on the root of my SD card (I like to organize all my ZIPs in folders)... Probably not a good idea haha. And I have always wiped boot last... never been bricked. I've been boot looped but that's always been a bad ZIP file's fault. And I make NANDROIDs for just such loops.
Sent from my Nexus S using Tapatalk 2
madd0g said:
Wiping storage ain't like wiping your ass, 1 wipe suffices.
Click to expand...
Click to collapse
Sent from my Nexus S using xda app-developers app
Braneless said:
I used to use wipe zips until some versions of CM9 refused to install/boot afterwards. Now I manually mount and format data, system, cache, and boot prior to installing a rom. Haven't had a problem since switching to this method.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Same thing for me.
And CWM wipes works perfectly. Don't be so lazy men.
Just do it this way.
One clicks and wipe zips will fail so you should learn what they are doing in case you need to do it yourself.
http://forum.xda-developers.com/showpost.php?p=27350690&postcount=4976
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII
When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.
Thanks for the info guys.
I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app
It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium
What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n
grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...
annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.
tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2
what is the best way to wipe to avoid problem with new rom? is it also necessary to format system?
ieisha said:
what is the best way to wipe to avoid problem with new rom? is it also necessary to format system?
Click to expand...
Click to collapse
Wipe data in recovery.
sfobrien said:
Wipe data in recovery.
Click to expand...
Click to collapse
dont format system?
ieisha said:
dont format system?
Click to expand...
Click to collapse
Rom builders format system prior to installing the Rom already.
Sent from my SCH-I535 using Tapatalk 2
mjdavis871 said:
Rom builders format system prior to installing the Rom already.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ok great thanks , well I just wanted to be sure since some people say different tthings
ieisha said:
dont format system?
Click to expand...
Click to collapse
No need to format system
For wiping, Wipe data/factory reset, then wipe cache partition and then wipe dalvik cache (under advanced menu). It may not all be necessary but I find many recommending all three with a new rom.
I'm thinking of selling my phone and want to make sure that it's been cleaned of all personal data. My phone is rooted and on CM 10.0
Do I just do the following:
>>Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik<<
Is it preferable to sell the phone with the stock ROM? If so how can I do that (assuming it's possible).
Thanks.
I would probably do a full wipe and flash the factory images thru fastboot and lock the bootloader. This will return it to brand new out of the box software.
Sent from my ns4g using Tapatalk 2
p1gp3n said:
I would probably do a full wipe and flash the factory images thru fastboot and lock the bootloader. This will return it to brand new out of the box software.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
This but format SD through the computer first. This will wipe everything and make it "Zip" again.
Sent from my Nexus S using xda premium
jayjay3333 said:
This but format SD through the computer first. This will wipe everything and make it "Zip" again.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I completely forgot that step, and it is most definitely important.
Sent from my ns4g using Tapatalk 2
The best way would be to flash the factory image, which will return everything stock and new. I have a guide here for it.
jayjay3333 said:
This but format SD through the computer first. This will wipe everything and make it "Zip" again.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I've been formatting the SD through CWM.
What is the difference between formatting in CWM or a computer? CWM sees to wipe it clean, or am I missing something?
billford said:
I've been formatting the SD through CWM.
What is the difference between formatting in CWM or a computer? CWM sees to wipe it clean, or am I missing something?
Click to expand...
Click to collapse
Formating through the computer will wipe and defragment it as well. It is a 'true" format than with CWM. CWM just wipes but not like through the computer.
Sent from my Nexus S using xda premium
jayjay3333 said:
Formating through the computer will wipe and defragment it as well. It is a 'true" format than with CWM. CWM just wipes but not like through the computer.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
i gotta question im selling my nexus s 4g rooted i want to keep the root on it but i want to wipe everything from it...should i just go into cwm and wipe factory reset and all that happy stuff? will this wipe everything?
subnoize soulja said:
i gotta question im selling my nexus s 4g rooted i want to keep the root on it but i want to wipe everything from it...should i just go into cwm and wipe factory reset and all that happy stuff? will this wipe everything?
Click to expand...
Click to collapse
I would format SD card through the computer than flash factory image from Google than root again by fastboot flash CWM and flash SU. This will ensure all is wiped and it will amaze the new user how fast it is. :thumbup:
Sent from my Nexus S using xda premium
DJBhardwaj said:
The best way would be to flash the factory image, which will return everything stock and new. I have a guide here for it.
Click to expand...
Click to collapse
does that guide you have the the nexus s 4g as well?
I have what seems like a very basic question on backing up using TWRP, and yet I havent been able to find this anywhere in the help threads.
When I am creating a backup it asks for what I want to backup: System, Data, Boot, Recovery, Cache, .android_secure.
Which of these do I want to make sure are checked? The first backup I did I left the default (which was only System and Data) and now I am unable to restore to that backup (I just get a blank, dark screen). Looking through the forums it seems I may need to flash boot.img in order to restore?
So does that mean in the future I should make sure to also check the Book option when I create backups? Any others?
Thanks.
system, data, boot
leave the other 3 unchecked
vincom said:
system, data, boot
leave the other 3 unchecked
Click to expand...
Click to collapse
Thanks again for all of your help over the last few days!
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? And is this fixable by flashing "boot.img" if I can find it somewhere?
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? > yes
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
vincom said:
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
Click to expand...
Click to collapse
You could probably just flash the same ROM you made the backup from and then just restore the data from that backup through TWRP. Then you'd be back to the same setup you tried to backup originally, right?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Jack_R1 said:
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Click to expand...
Click to collapse
My initial backup was made just with the default - first two boxes ticked. Unfortunately I now cannot get that backup to recover and boot, which is why I am asking. What else might be the cause or how would you suggest I try to solve?
Also, apologies but I dont understand what you mean when you say "Backing up recovery in recovery is useless, though." Do you mean this isnt the best way to make a backup/nandroid to recover to?
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Jack_R1 said:
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Click to expand...
Click to collapse
Thanks. I think I misunderstood your initial post. When you said "system, data, boot" advice might fail me, I thought you meant NOT to backup boot. But I think you meant to ALSO backup .android_secure, not to avoid backing up boot.
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
lirong said:
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
Click to expand...
Click to collapse
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Click to expand...
Click to collapse
LOL. Can't we all just get along.
Since I'm not one to speak for others I'll only guess that what he was trying to get at is restoring only erases the boot.img. It then restores boot.img, system, data, android.secure, and cache. So in theory it doesn't actually erase any of the remaining partitions. It just writes over them. Whether or not this leaves any residual parts of any of the partitions has been a source of debate for quite some time. If it does format the partitions before restore there is no indication textually that I have seen.
Carry on.
EDIT: I might as well point this out before some one else does. The restores I stated above where done from CWM not TWRP. I forget what the thread was originally about. For that I apologize. The logic behind the post stands for either recovery though.
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Maybe. But a couple of points. First, I've never had any issues. Second, have you watched what happens when you restore?
Wiping system.....
Formatting system....
Restoring system....
Wiping data....
Formatting data....
Restoring data....
Restoring boot...
This is on twrp 2.3.3.0 and 2.4.0.0. So technically it does the wipes for you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So basically you have no idea what you're saying. I guess I'll go back to my being concise point
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You're obviously a CWM guy. I'm a TWRP guy. Both are good recoveries and used by many. So use what you're comfortable with and you know works.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app