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
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
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
ok i will start by saying i have searched everything in forums and could not find this problem
my goal is to install CM 10.1 i have followed the official guide on the forums but after it is installed it boots to image that shows CM booting but it takes about 10 min before it just resets and continues this cycle and only way to fix is to do stock firmware via odin after which it works fine i can even flash via CWM but only official firmware will work without this problem can someone help me with this if more info is needed plz tell me i am rather new to forums
Are you wiping everything before you flash?
Sent from my SAMSUNG-SGH-I727 using xda premium
spitfire2425 said:
Are you wiping everything before you flash?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yes i have wiped cache and dalvik and system
crashburn833 said:
ok i will start by saying i have searched everything in forums and could not find this problem
my goal is to install CM 10.1 i have followed the official guide on the forums but after it is installed it boots to image that shows CM booting but it takes about 10 min before it just resets and continues this cycle and only way to fix is to do stock firmware via odin after which it works fine i can even flash via CWM but only official firmware will work without this problem can someone help me with this if more info is needed plz tell me i am rather new to forums
Click to expand...
Click to collapse
Did you check MD5 before flashing? Could be a bad download.
Usually boot loop issues are due to left overs from your previous rom so,
If you're on CWM recovery , use this ORDER :
1.Reset user data/factory reset
2.Format System
3.Format Data
4.Format Cache
5.Format SD card (back up your important files first)..
Then flash the rom ... Don't wipe dalvik it's already in /data
This applies not just to CM10 , use this procedure to any rom flash or any nandroid restore ...
mahanddeem said:
Usually boot loop issues are due to left overs from your previous rom so,
If you're on CWM recovery , use this ORDER :
1.Reset user data/factory reset
2.Format System
3.Format Data
4.Format Cache
5.Format SD card (back up your important files first)..
Then flash the rom ... Don't wipe dalvik it's already in /data
This applies not just to CM10 , use this procedure to any rom flash or any nandroid restore ...
Click to expand...
Click to collapse
still did not work
You don't have to wipe sdcard
Sent from my SGH-I727 using xda premium
crashburn833 said:
still did not work
Click to expand...
Click to collapse
In such case,you have a problem somewhere else...Redownload the rom check its md5 and try again...Make sure you're downloading the correct rom for your device...
I'm trying to wipe my One X, but it is refusing to do so, all my stuff stays there and the phone is extremely sluggish.
What am I doing wrong?
I'm wiping from CWM 6.0.3.1
Ratzu said:
I'm trying to wipe my One X, but it is refusing to do so, all my stuff stays there and the phone is extremely sluggish.
What am I doing wrong?
I'm wiping from CWM 6.0.3.1
Click to expand...
Click to collapse
Download TWRP 2.3.3.1
Fastboot flash recovery recoveryfilename.zip
Fastboot erase cache
Fasboot reboot bootloader
Go to recovery, then wipe.
exad said:
Download TWRP 2.3.3.1
Fastboot flash recovery recoveryfilename.zip
Fastboot erase cache
Fasboot reboot bootloader
Go to recovery, then wipe.
Click to expand...
Click to collapse
Didn't work.
Didn't wipe?
Sent from my One X using xda app-developers app
exad said:
Didn't wipe?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Nope.
Is there an error or does it complete successfully?
Sent from my One X using xda app-developers app
Ratzu said:
Nope.
Click to expand...
Click to collapse
What are you wiping? Just cache? just dalvik cache? Make sure you have a spare rom on your pc and then wipe everything. Cache,Dalvik cache, sytem, factory reset,and sdcard. Guaranteed all your stuff will be gone. Including your rom. Youll have to mount your sdcard afterwards and copy a rom to the sd and flash it afterwards.
ImagioX1 said:
What are you wiping? Just cache? just dalvik cache? Make sure you have a spare rom on your pc and then wipe everything. Cache,Dalvik cache, sytem, factory reset,and sdcard. Guaranteed all your stuff will be gone. Including your rom. Youll have to mount your sdcard afterwards and copy a rom to the sd and flash it afterwards.
Click to expand...
Click to collapse
Wiping sdcard returns an error, but everything else "works" but doesn't do anything.
Ratzu said:
Wiping sdcard returns an error, but everything else "works" but doesn't do anything.
Click to expand...
Click to collapse
I'm at a loss sorry. If you didn't check the md5, that would be a good start, just to ensure it was a good download. Also, hopefully it was twrp 2.3.3.1 or earlier as higher versions have wiping issues.
Sent from my One X using xda app-developers app
I'm voting operator error
If your on twrp 2.3.3.1 mount storage and format sd on a pc... Copy Rom to sd and flash away. With all your stuff gone
Sent from my HTC One X using xda app-developers app
31ken31 said:
I'm voting operator error
If your on twrp 2.3.3.1 mount storage and format sd on a pc... Copy Rom to sd and flash away. With all your stuff gone
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
What is the best way to wipe it? Fastboot?
What can't I delete, if I have to do it manually?
And how do I mount storage from recovery, can you give me a detailed process? I've never had a problem like this.
Ratzu said:
What is the best way to wipe it? Fastboot?
What can't I delete, if I have to do it manually?
And how do I mount storage from recovery, can you give me a detailed process? I've never had a problem like this.
Click to expand...
Click to collapse
The tab that says mount... And it won't make a difference if u delete one thing at a time or format it. If you can't find mount in recovery stop screwing with the phone. You haven't read enough. I don't mind helping but.... Do try and help yourself before asking. These phones can be tricky, spend a few hours getting a grasp then I'll bet you could handle it on your own
Sent from my HTC One X using xda app-developers app