Devs, please specify on your flashing instructions for users of CWM 6.0.x.x and above, that TDJs superwipe and cache wipe script will break CWM. TDJ never removed the fixes he included in the script for CWM 5.0.2.7 and they are the root of the issue of the recovery breaking when using the scripts with CWM 6.0+. They are only meant for CWM 5.0.2.7 AND TWRP 2.2+ and people do not know this. As you may or may not know using these on any version of CWM other than 5.0.2.7 BREAKS THE RECOVERY!!! The forums are piling up with people complaining about broken CWM installations.
If you wish to continue using TDJ's wipe scripts, Flash TWRP 2.3.1.1, which you can DL here: https://www.dropbox.com/s/qibb4qrp4zdc76a/TWRP-2.3.1.1-hercules.zip
or visit the TWRP 2.3.1.1 in it's own thread here: http://forum.xda-developers.com/showthread.php?t=1768742
For users of CWM 6.0+, please refer to and use the flashing instructions provided within this thread instead of using the wipe scripts:
http://forum.xda-developers.com/showthread.php?t=1926754
They work the exact same way whether you're on CWM or TWRP.
A few pointers..
-Please stop fixing permissions and cache wiping after flashing a ROM. This is only necessary if you're having issues with the ROM AFTER you have installed it.
-IF you are using any of TDJs ROMS ONLY use CWM 5.0.2.7 OR TWRP 2.2+. His ROMS automatically flash the aforementioned superwipe script, causing reboot hangs. The only method to fixing the reboot hang is to flash TDJ's Cache Wipe and this breaks CWM's ability to flash ANYTHING correctly. Forcing the user to have to ODIN back to stock.
The forums are getting cluttered up with people having issues that can be completely avoided if the specifics are stated within your flashing instructions.
Instructions have been edited and specified further upon to avoid further confusion.
Sent from my SGH-T989 using xda premium
good info...
Flashable wipe scripts are made by many different devs on multiple devices. Most of the time the superwipe scripts do a better job between rom flashing .. to be honest even though its not needed it is a convenience for some. I use a superwipe script on my wife's sensation all the time between flashing .. I'd say if the script breaks the recovery then the recovery is borked...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I think the info is good to put out there, but the thread title and the way you worded this needs to be edited.. I mean your not a dev and i mean this in a nice way.. you don't get to tell them what they should and should not do.. just sayin..
AND the cache wipe/ fix perm script was made because CWM wasn't doing it correctly. Yes that is correct..
The Superwipe was made for yes the same reason, however its also to make sure that all of the partitions get wiped and aligned correctly before a flash... just like every other superwipe for every other phone (there is many many of these scripts..)... still relevant and useful..
Bottom line is newer versions of CWM apparently doesn't play well with these kinds of scripts.. and that to me is an issue with the recovery..
HOWEVER ya'll should stop arguing over this, it makes you bolth look a bit childish and petty..
Alrighty then...I have done a full sweep of this thread. No more fighting whats so ever. Digital bliss everyone is entitled to their own opinions...that does not mean you can voice them without getting lashed at. RushAOZ...not everyone is having this issue obviously but the thread is a great reference to those that are.
Oh.. btw.. fixing perm and wiping cache is a good idea after a rom flash... your giving bad Info here.. It insurers that there is not going to be anything in your dalvik cache that could conflict. And doing fix fix permissions just makes sure that everything is set and aligned correctly. If anything it 100% does not cause issues and is recommended ...
You should really take that out of your post
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
Oh.. btw.. fixing perm and wiping cache is a good idea after a rom flash... your giving bad Info here.. It insurers that there is not going to be anything in your dalvik cache that could conflict. And doing fix fix permissions just makes sure that everything is set and aligned correctly. If anything it 100% does not cause issues and is recommended ...
You should really take that out of your post
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Sorry, but that's absolutely unnecessary and actually does cause issues.
To do these steps after the ROM has loaded and has been under use causes no issues and does fix any issues you might have. For example I just flashed cm10 nightly from fresh. After I had completely set up my phone and installed and restored app data I noticed my phone was charging extremely slow. Fixed permissions and everything's in order now. But wiping cache and fixing permissions immediately after flashing, without loading the ROM up is pointless. Once your ROM is flashed after initial wiping all files are set in place and ready to go as the developer intended. Wiping caches and fixing permissions right after ROM intallation might offset the original boot sequence and cause issues.
Look at hate410s post for proof of this. He took these same steps, and a few more unneeded ones and he can't get a stable install to save his life.
If you wipe properly or run TDJs wipe gets the phone ready for any ROM installation and if done correctly will install the ROM as the developer intended. If you have issues up initial boot after wiping correctly, chances the flaw lies in the ROM itself. If that makes any sense. Its only logic.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Sorry, but that's absolutely unnecessary and actually does cause issues.
To do these steps after the ROM has loaded and has been under use causes no issues and does fix any issues you might have. For example I just flashed cm10 nightly from fresh. After I had completely set up my phone and installed and restored app data I noticed my phone was charging extremely slow. Fixed permissions and everything's in order now. But wiping cache and fixing permissions immediately after flashing, without loading the ROM up is pointless. Once your ROM is flashed after initial wiping all files are set in place and ready to go as the developer intended. Wiping caches and fixing permissions right after ROM intallation might offset the original boot sequence and cause issues.
Look at hate410s post for proof of this. He took these same steps, and a few more unneeded ones and he can't get a stable install to save his life.
If you wipe properly or run TDJs wipe gets the phone ready for any ROM installation and if done correctly will install the ROM as the developer intended. If you have issues up initial boot after wiping correctly, chances the flaw lies in the ROM itself. If that makes any sense. Its only logic.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Lmao.. NO.. I'm not going to argue with you.. but your wrong and spreading miss information.
A uid mismatch fix, commonly referred to as a fix permission just makes sure the permissions are set correct.. it can't mess up anything..
and depending on what you have flashed and if you have or have not factory reset doing a cache wipe will ensure there will not be any conflicts in your dalvik cache.. also can't mess up anything..
I think you really should learn what these thing are and what they do before you make comments about them.
The fact that you think there is special things that can be messed up on first boot shows your lack of knowledge.. yes devs can have scripts run at boot, for example a zip alignment .. however regardless of if you did or did not do a wipe and fix perm these things will still run, they are just boot scripts.. lmao..
..
garth719 said:
+1 fixing permissions right after a fresh install does absolutely nothing. You have to do it once the rom has settled in. Just to prove, if you try to fresh install a ROM with twrp and hit fix permissions it will say ABORTED.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Doesn't say aborted for me... and I'm using twrp.. it does a permission fix with no issue..
And its been a recommended step since the G1.. but do what ya want..
Either way telling people not to do it or a chache wipe is still spreading bad information ..
PJcastaldo said:
Lmao.. NO.. I'm not going to argue with you.. but your wrong and spreading miss information.
A uid mismatch fix, commonly referred to as a fix permission just makes sure the permissions are set correct.. it can't mess up anything..
and depending on what you have flashed and if you have or have not factory reset doing a cache wipe will ensure there will not be any conflicts in your dalvik cache.. also can't mess up anything..
I think you really should learn what these thing are and what they do before you make comments about them.
The fact that you think there is special things that can be messed up on first boot shows your lack of knowledge.. yes devs can have scripts run at boot, for example a zip alignment .. however regardless of if you did or did not do a wipe and fix perm these things will still run, they are just boot scripts.. lmao..
Click to expand...
Click to collapse
First of all there's no need to get riled up. I've been on these forums and flashing phones since 2008. I think I know a thing or 2 about it.
As far as everything you said that could go wrong, to me is easily avoided with a full formatting of your partitions. If you have a clean canvas to work with, you should have 0 errors in your install. Unless the ROM itself has any flaws of course. And if that's the case you shouldn't be flashing it.
Well to each his own. I make these decisions based on the fact that I've owned about 7 android phones and not one developer or flash instruction I've read called for an immediate cache wiping and permission fix as soon as your ROM is installed. Not my G2, Epic 4g, GSII, Nexus S 4g, Evo 4g, Evo 3d, and the plethora of other phones L
I've flashed for people which include a Galaxy Nexus, Epic Touch 4g, Vibrant, GSIII and an international Galaxy S2.. Only on this phone.
And the reason I say it's unnecessary is because I'm one of those people that NEVER have issues except issues that are already established by the developer in the op.
I've flashed every ROM in this forums, using my flash instructions (which really aren't mine, it's just the old fashioned, right way to wipe) and every ROM has worked flawlessly with no freak errors.
To me, just making sure that you've properly formatted all your partitions is all the ROM needs to install and work as intended.
And it's been working like a charm for me since 2008. Take my word for it or not. But like I said. A simple, proper wipe is all you need to for a ROM to install error free. Look at my post history. You'll find 0 posts having to do with any issues that I'm not already supposed to have. I was even one of those people that haven't had an RR or SoDs since CM10 nightlies released. But like I said, to each his own.
Btw boot loops are one of the common issues people get when wiping cache and fixing permissions without letting the ROM boot up for the first time. You can find plenty of those in the TW rom threads.
Sent from my SAMSUNG-SGH-T989 using xda premium
01. Download ROM (Link is Below)
02. BACKUP ALL APPS with preferred method (ie: Rom Toolbox, Titanium, My Backup, etc..)
03. Place ROM on ROOT of your SD card. (ie: /sdcard)
04. Boot into Recovery Mode
05. Do a NAND BACKUP!!!
06. Flash DARKSIDE.SUPER.WIPE (OPTIONAL - ROM will do this by default)
07. Flash an ICS ready radio (Links below)
08. Flash ROM.
09. After flashing is complete, Reboot...
10. Let device sit for 10min without touching, then reboot.
11. Done!
These are flashing instructions from TDJ himself. Not only did he have the most popular rom for the T989 (with his Evolution v8 thread having more than 1.2 million views...) but he's widely considered the best dev this phone has ever had. Not only that he's not a new guy and has been around since the mytouch days. I don't see any instructions in there about wiping cache and fixing permissions immediately after ROM installation, do you?
RushAOZ said:
01. Download ROM (Link is Below)
02. BACKUP ALL APPS with preferred method (ie: Rom Toolbox, Titanium, My Backup, etc..)
03. Place ROM on ROOT of your SD card. (ie: /sdcard)
04. Boot into Recovery Mode
05. Do a NAND BACKUP!!!
06. Flash DARKSIDE.SUPER.WIPE (OPTIONAL - ROM will do this by default)
07. Flash an ICS ready radio (Links below)
08. Flash ROM.
09. After flashing is complete, Reboot...
10. Let device sit for 10min without touching, then reboot.
11. Done!
These are flashing instructions from TDJ himself. Not only did he have the most popular rom for the T989 (with his Evolution v8 thread having more than 1.2 million views...) but he's widely considered the best dev this phone has ever had. Not only that he's not a new guy and has been around since the mytouch days. I don't see any instructions in there about wiping cache and fixing permissions immediately after ROM installation, do you?
Click to expand...
Click to collapse
His roms are set up to run the cache wipe scripts automatically during a flash.. so yes it is doing a fix perm..
AND while i agree he is talented, I would not call him the best on our device. Especially when guys like whitehawx are around.. or Eugene.. or any of the other guys who have been around for YEARS.. but thats an opinion..
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
RushAOZ said:
First of all there's no need to get riled up. I've been on these forums and flashing phones since 2008. I think I know a thing or 2 about it.
As far as everything you said that could go wrong, to me is easily avoided with a full formatting of your partitions. If you have a clean canvas to work with, you should have 0 errors in your install. Unless the ROM itself has any flaws of course. And if that's the case you shouldn't be flashing it.
Well to each his own. I make these decisions based on the fact that I've owned about 7 android phones and not one developer or flash instruction I've read called for an immediate cache wiping and permission fix as soon as your ROM is installed. Not my G2, Epic 4g, GSII, Nexus S 4g, Evo 4g, Evo 3d, and the plethora of other phones L
I've flashed for people which include a Galaxy Nexus, Epic Touch 4g, Vibrant, GSIII and an international Galaxy S2.. Only on this phone.
And the reason I say it's unnecessary is because I'm one of those people that NEVER have issues except issues that are already established by the developer in the op.
I've flashed every ROM in this forums, using my flash instructions (which really aren't mine, it's just the old fashioned, right way to wipe) and every ROM has worked flawlessly with no freak errors.
To me, just making sure that you've properly formatted all your partitions is all the ROM needs to install and work as intended.
And it's been working like a charm for me since 2008. Take my word for it or not. But like I said. A simple, proper wipe is all you need to for a ROM to install error free. Look at my post history. You'll find 0 posts having to do with any issues that I'm not already supposed to have. I was even one of those people that haven't had an RR or SoDs since CM10 nightlies released. But like I said, to each his own.
Btw boot loops are one of the common issues people get when wiping cache and fixing permissions without letting the ROM boot up for the first time. You can find plenty of those in the TW rom threads.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
again.. your spreading incorrect information and someone should take this information down.. Im glad you've been here a whopping year longer than I.. I have also owned several devices and have done a cache wipe and a fix perm after flashing since the beginning and it has NEVER cause an issue..
INFACT most of the time people report a boot loop the first thing they are told is to do a reboot and wipe cache and fix permission and it usually fixes the boot loop..
And here is an example from a different Devs thread ptmr, whos jedi roms are very popular..
Instructions
TWRP Recovery Recommended!
ALWAYS FULL WIPE!
-Download ROM
-Backup your apps with preferred method(app2zip is great)
-Nandroid
-Wipe data ( factory data reset)
-Wipe system (Format system (in mounts/storage) if on CWM)
-Flash ROM
-Wipe cache/Dalvik
-Fix Permissions
-(USE DARKSIDE CACHE SCRIPT IF STILL ON CWM RECOVERY)
-Boot system and DO NOT TOUCH FOR 10 MIN
-After the 10 min, reboot phone and enjoy the Mind Trick
-DO NOT RESTORE DATA!!!
PJcastaldo said:
His roms are set up to run the cache wipe scripts automatically during a flash.. so yes it is doing a fix perm..
AND while i agree he is talented, I would not call him the best on our device. Especially when guys like whitehawx are around.. or Eugene.. or any of the other guys who have been around for YEARS.. but thats an opinion..
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
again.. your spreading incorrect information and someone should take this information down.. Im glad you've been here a whopping year longer than I.. I have also owned several devices and have done a cache wipe and a fix perm after flashing since the beginning and it has NEVER cause an issue..
INFACT most of the time people report a boot loop the first thing they are told is to do a reboot and wipe cache and fix permission and it usually fixes the boot loop..
And here is an example from a different Devs thread ptmr, whos jedi roms are very popular..
Instructions
TWRP Recovery Recommended!
ALWAYS FULL WIPE!
-Download ROM
-Backup your apps with preferred method(app2zip is great)
-Nandroid
-Wipe data ( factory data reset)
-Wipe system (Format system (in mounts/storage) if on CWM)
-Flash ROM
-Wipe cache/Dalvik
-Fix Permissions
-(USE DARKSIDE CACHE SCRIPT IF STILL ON CWM RECOVERY)
-Boot system and DO NOT TOUCH FOR 10 MIN
-After the 10 min, reboot phone and enjoy the Mind Trick
-DO NOT RESTORE DATA!!!
Click to expand...
Click to collapse
Yes, TDJs super wipe formats and wipes cache BEFORE ROM installation, not afterwards.
Like I said to each his own whatever works for you.
Also this info doesn't need to be taken down. Maybe those flashing steps apply to the Jedi ROMs specifically, because of you check all the other ROMs these steps aren't listed as necessary. Only the current crop of TW ROMs. So we both may be correct and in the end it probably doesn't matter. I've flashed the Jedi ROMs myself and didn't do anything other than flashing the superwipe script, flashing the ROM and reboot. No issues. The step might just be a precautionary measure.I know for a fact that with AOSP based ROMs the step is unnecessary. You don't even need to wait the initial 10 minute time like with TW ROMs either lol. Like I said whatever works for ya works man.
Happy flashing folks!
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Yes, TDJs super wipe formats and wipes cache BEFORE ROM installation, not afterwards.
Like I said to each his own whatever works for you.
Also this info doesn't need to be taken down. Maybe those flashing steps apply to the Jedi ROMs specifically, because of you check all the other ROMs these steps aren't listed as necessary. Only the current crop of TW ROMs. So we both may be correct and in the end it probably doesn't matter. I've flashed the Jedi ROMs myself and didn't do anything other than flashing the superwipe script, flashing the ROM and reboot. No issues. The step might just be a precautionary measure.I know for a fact that with AOSP based ROMs the step is unnecessary. You don't even need to wait the initial 10 minute time like with TW ROMs either lol. Like I said whatever works for ya works man.
Happy flashing folks!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Ill agree with you when it comes to that waiting ten minutes thing.. I personally think its a myth..
but you still get a few of these..
And im sorry, im not trying to argue with you.. But neither you nor I are a dev, we are just flashers who have much knowledge.
Point being a cache wipe and a fix perm is not required, but WILL prevent issues and CAN NOT IN ANY WAY cause a problem.. your OP is wrong and should be edited to reflect that.
PJcastaldo said:
Ill agree with you when it comes to that waiting ten minutes thing.. I personally think its a myth..
but you still get a few of these..
And im sorry, im not trying to argue with you.. But neither you nor I are a dev, we are just flashers who have much knowledge.
Point being a cache wipe and a fix perm is not required, but WILL prevent issues and CAN NOT IN ANY WAY cause a problem.. your OP is wrong and should be edited to reflect that.
Click to expand...
Click to collapse
Haha you just made me remember a specific part of my claims I didn't mention. I should have clarified. I'm talking about flashing TDJs wipe cache immediately after flashing a ROM. I've done this myself and came up with boot loops. Which is probably due to CWM 6.0.1.4 AND 6.0.1.5s intolerance for the fixes TDJ included to fix the crap CWM 5.0.2.7 couldn't get done =D
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Haha you just made me remember a specific part of my claims I didn't mention. I should have clarified. I'm talking about flashing TDJs wipe cache immediately after flashing a ROM. I've done this myself and came up with boot loops. Which is probably due to CWM 6.0.1.4 AND 6.0.1.5s intolerance for the fixes TDJ included to fix the crap CWM 5.0.2.7 couldn't get done =D
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Which brings back the main point of your thread.. I am telling you that these kinds of scripts are not only made for our device, but many others as well. The reason those specific recovery's don't flash them properly is because they are borked...
PJcastaldo said:
Which brings back the main point of your thread.. I am telling you that these kinds of scripts are not only made for our device, but many others as well. The reason those specific recovery's don't flash them properly is because they are borked...
Click to expand...
Click to collapse
Nah the problem with the scripts isn't the scripts themselves. They're awesome! Who wouldn't want a on click solution to wiping their partitions? Its the fixes TDJ included to fix CWM 5.0.2.7s faults, which have been fixed in CWM 6+, which is why they cause issues. TWRP is immune to these fixes and they work perfectly. So to any users out there, if you have CWM 6+, do t use the wipes. Any TWRP users, the scripts work perfectly well and won't ruin anything. Thanks for helping me clarify that Castaldo. The recoveries used with our phones are very different and call for different flashing instructions. Which is the point to my post. Devs, please clarify this! And your threads won't be full of crazy issues that can easily be avoided lol
I'm busy working on some beer and liquor with friends ATM. Gonna get back to that lol
enjoy your weekend and happy flashing folks!
I'll fix the OP with these new changes ASAP.
Sent from my SAMSUNG-SGH-T989 using xda premium
The more you guys debate, the more we learn. I'm trying to think of a way to feed the fire.... lol
Sent from my SGH-T989 using xda app-developers app
bzlik88 said:
The more you guys debate, the more we learn. I'm trying to think of a way to feed the fire.... lol
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
feel free.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Related
First off if you're on ANY recovery that isn't CWM 5.0.2.7 you DO NOT NEED TDJS SUPER WIPE OR CACHE WIPE SCRIPTS!!!! Seriously stop flashing these people you're filling up threads with problems caused by both of these scripts and bad flashing methods. Here's how to PROPERLY flash a ROM..
If on CWM 6.0.x.x
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
If you're on a Cyanogenmod nightly a full wipe IS NOT REQUIRED. The proper method of dirty flashing is just wiping cache, ( NOT FORMAT CACHE IN MOUNTS & STORAGE )
wiping dalvik and flashing your ROM. Simple as that.
If using TWRP 2.2+ the steps are essentially the same or use TDJs wipe scripts. They work perfectly fine with TWRP. Feel free to wipe 2x or even 3x if it makes you feel safer about your installation.
And THAT'S IT. People are cluttering up threads with issues than can totally be avoided by flashing the right way. I hope this helps some of you iron out these insane tiny quirks I keep reading about.
Happy flashing folks.
EDIT:
I forgot to note.. if you're still using one of TDJs roms or any other rom that automatically wipes with TDJs SUPER CACHE WIPE, do NOT use any other recoveries other than CWM 5.0.2.7 or TWRP 2.2+. With any other recovery such as CWM 6.0.x.x+, the wipe script breaks the roms ability to reboot properly and the only way to solve this is to use TDJs CACHE WIPE which in turn breaks your recoveries ability to work properly.
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks man this was needed. Yes threads get filled with this so often. I dirty flash like you mentioned accept I format system first. I also clean flash like you mentioned but never formatted cache and dalvik just system. That's good to know. Thanks
But I will add those new steps. I format system when dirty flashing because on the cm10 Site they mentioned that.
Again thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
I edited OP with a little bit more information for safer flashing.
Sent from my SGH-T989 using xda premium
Sad we need to keep telling people how to flash. If you are not sure what you are doing I think you should be very careful before you destroy your expensive toy. Everyone should have an idea on how to flash and restore from a bad flash before they even root. Also as my sig says let Google be your friend people if you run into issues instead of running to a thread and clogging it up...
Thanks for post and this is a bump to keep it on page 1 and hopefully more people will notice it.
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Goofy317 said:
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Click to expand...
Click to collapse
Can you boot into recovery at all? If you can.. download the TWRP 2.2.2.0 zip in its thread and flash it. Its going to hang in the install process but should say twrp has been installed. At that point reset your phone by holding the power button. As soon as you feel the phone vibrate hold down both volume buttons and you should boot into TWRP recovery.
Sent from my SAMSUNG-SGH-T989 using xda premium
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
Darkside superwipe will only mess your ROMs ability to reboot on touchwiz ROMs. The only way to fix this is flashing the darkside cache wipe which WILL break clockwork mod 6.0.1.4 like the user above. Point is.. don't use either scripts at all on CWM. Wipe the old fashioned way.
Sent from my SAMSUNG-SGH-T989 using xda premium
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
I agree. even after switching to twrp I still find the script useful. But op warning about using script with cwm version 6xxx might be true. I have issue with boot when i was on cwm 6 and i had to Odin cwm 5.0.2.7 again to get into recovery menu.
Sent from my SGH-T989 using xda app-developers app
Thanks, always forgot the formatting steps
ultratt said:
Thanks, always forgot the formatting steps
Click to expand...
Click to collapse
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
RushAOZ said:
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Davy Jones said:
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Click to expand...
Click to collapse
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
RushAOZ said:
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Oh cool, I was already really liking TWRP and this makes it even better.
This thread should be a sticky.
Khameleon said:
This thread should be a sticky.
Click to expand...
Click to collapse
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
apicia said:
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
Click to expand...
Click to collapse
Just go into CWM and wipe cache in the main menu and dalvik in the advanced menu. To be honest though you don't need to do this whatsoever. Only when dirty flashing a new nightly. In my experience atleast lol as far as gapps go..
http://goo.im/gapps/gapps-jb-20121011-signed.zip
These should work just fine
Sent from my SAMSUNG-SGH-T989 using xda premium
Bump fer new users yo
Sent from my SGH-T989 using xda premium
Bump for new users
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks
Does any one here know if some of the Kernal cleanser zips from the s2 for TMO would work on the s3? If not are there any similar options?
Also is there a davlik wipe that works properly on the s3? Similar to the dark side zips. Cwm is not doing so correctly.
Sent from my SGH-T999 using xda premium
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
This is the link for superwipe for the Hercules
http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
Sent from my SGH-T999 using xda premium
Well not exactly what I was looking for but it will work for clean flashes. Thanks kind sir. This is from the same dev as the s2 so it's solid I am sure.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
I have been using TWRP since I rooted my phone back in June, have not had 1 issue with it. Everything works flawlessly, I have flashed almost every AOKP, CM10, TW ICS & TW JB ROM out there thru TWRP and never lost my IMEI and the wipe functions in it work just fine. I usually wipe cache/delvik, system & factory reset 3 times. For me it seems to wipe pretty fast ( that's why I do it 3x ).Just to be safe.
belial20xx said:
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Well isn't this normal since there is no external sd ext partition? I mean sure one could write a simple zip to delete /data/dalvik-cache.
And there really isn't a way to check it either. Cause I don't think adb works in recovery mode.
Sent from my SGH-T999 using Tapatalk 2
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Aerowinder said:
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Click to expand...
Click to collapse
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
I made a dalvik cache wiper.
If you notice when you use CWM to clear dalvik cache, then reboot, it doesnt say android is upgrading at all. Making me think it doesnt work.
But when you just flash my script, it says its upgrading.
the zip is simple, all it does is delete_recursive("/data/dalvik-cache/") and thats it.
elesbb said:
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
Click to expand...
Click to collapse
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Aerowinder said:
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Click to expand...
Click to collapse
So did i.. but it optimized the same amount of apps that the "wipe cache" option does. I seriously wonder now if they are one in the same. Like if they are coded to wipe /cache and /data/dalvik-cache. Cause when using my zip, i only optimize 58 apps.
Hi all,
First post on xda here. I was trying to update my frosty jelly bean v6 to v7 via OTA update, installed the package and it restarted itself in CWM mode but it said something alone the lines of "failed update... update file not found." I downloaded the v7 package from the developer's link and was thinking about just installing it from zip on sd card.
Why can't it update? If I install v7 from the zip and wipe cache will that work too or no?
Sent from my SGH-T999 using xda app-developers app
Install from CWM yourself, as you suggested.
Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app
timma1 said:
Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This what you do after you put the zip in the scard...make sure your in recovery..
Wipe data/factory reset
Wipe cache & dalvik
Install Rom
Wipe cache and dalvik (again)
Fix Permissions
Reboot & let it sit for 5-10 mins (Don't touch anything!)
Reboot & enjoy!
*Please perform a full wipe for v7!
Hope this helps.
Thanks. Yeah I saw that on the dev thread... I followed those steps when i first flashed the frosty JB. But my question is do i really have to do a data wipe even for every version update? That seems to be a lot of hassle...
Sent from my SGH-T999 using xda app-developers app
Wipe Dalvik and dirty flash it. 4.1.1 > 4.1.2 = no clean flash necessary. I guess it's the devs' fault for spreading all of this clean flashing nonsense that's been more contagious than the bubonic plague. Like the IMEI loss rumors. It's only necesary if: going from ICS to JB, or vice versa. Or if you're having some major issue that no one else is having. Which is rare.
Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app
timma1 said:
Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
What is the version of your CWM? i think its need to be updated.
3.0.7
Sent from my SGH-T999 using xda app-developers app
Yup, update it, the latest version is 6.xxx. i encountered the same error when i tried to install cm10 with an outdated cwm.
For a noob, you can easily update cwm by downloading and installing ROM MANAGER using your phone from PLAYSTORE.
launch the rom manager app then you can see an option there to update cwm
Id like to make a quick point on the dirty vs clean flashing.
Usually, it is correct that dirty flashing is ok except when jumping between android versions. (Even then, when going forward in version, its still often ok to dirty flash).
However, in the cases we see here this is not necessarily true. I am of course referring to our jb leaks and roms based on them.
Dirty flashing these after an update can cause problems. Many people, myself and the devs themselves included, have seen where a number of bugs would be nonexistent if you just did a clean flash. These are experimental builds based on leaked firmware. I'm certain the devs you guys are referring to recommend a clean flash for two reasons. First, it simply makes their rom operate much better. Second, and most important from a dev standpoint, if you dirty flashed, and are experiencing bugs, there is nothing the dev can really do for you. In fact, unless you clean flashed the rom, you shouldn't even report on bugs unless you find a fix for it.
Another thing to consider is a couple if these roms are based not just on a leak, but on multiple leaks often from more than one carriers device! Due to this, if you dirty flash you are much more likely to have bugs show up. It really depends on what has been changed, updated and rebased, and no one can predict how uts going to act.
No one says you cannot dirty flash these roms. Many have done so with few to no issues. But, if you do, and you run into problems please do not blame the dev or expect him to fix the problem unless it is being reported by the majority of users.
Not trying to argue or say anyone is right or wrong. I'm just trying to clear up the reason for the dev suggestion to clean flash.
Hope it helps!
Sent from my SGH-T999 using xda app-developers app
Hi all, ive had my Tmobile samsung galaxy s2 for awhile now, and i finally decided to root it (and did it successfully) a few days ago (yay)
Ive done a bit of research for what I can do while rooted, basically after CPU setting, save battery life when idle... Simple things
But ive been meaning to try flashing a ROM. But I want to make sure i know absolutely everything needed to know to flash one. I had a samsung tmobile sidekick that I was able to root and flash Gingerclone on, but I remember it had alot of little details while installing that simply missing one could seriously screw up your phone
So first off, if anyone has had the sidekick: Is flashing/ installing roms as complex on the sgh-t989 as it is on sidekick 4g?
And secondly... After rooting my galaxy, i no longer have the stock android recovery (obviously)...... Instead it is replaced with CWM-based recovery (i think 5.0.2.2?). Is there a difference between this and Clockworkmod recovert (which should show an orange screen)?
I wanted to use ROM manager but opted not to when it told me that I "needed clockworkmod recovery installed" to work.
A little help, please?
Thanks!
heyitsmeyo2 said:
Hi all, ive had my Tmobile samsung galaxy s2 for awhile now, and i finally decided to root it (and did it successfully) a few days ago (yay)
Ive done a bit of research for what I can do while rooted, basically after CPU setting, save battery life when idle... Simple things
But ive been meaning to try flashing a ROM. But I want to make sure i know absolutely everything needed to know to flash one. I had a samsung tmobile sidekick that I was able to root and flash Gingerclone on, but I remember it had alot of little details while installing that simply missing one could seriously screw up your phone
So first off, if anyone has had the sidekick: Is flashing/ installing roms as complex on the sgh-t989 as it is on sidekick 4g?
And secondly... After rooting my galaxy, i no longer have the stock android recovery (obviously)...... Instead it is replaced with CWM-based recovery (i think 5.0.2.2?). Is there a difference between this and Clockworkmod recovert (which should show an orange screen)?
I wanted to use ROM manager but opted not to when it told me that I "needed clockworkmod recovery installed" to work.
A little help, please?
Thanks!
Click to expand...
Click to collapse
There the same
Sent from my HTC PH39100 using xda app-developers app
XxSHaDoWxSLaYeRxX said:
There the same
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Okay, great! Glad it was so simple lol.
Now about my other question... Let me explain. When I would install a custom ROM on my sidekick, i remember having to do all sorts of things like unmount system/ unmount SD card before installing and remount them after (i dont remember the exact methods... Dont quote me on that).
I know the general procedure of basically Wiping data, Wiping cache, Wiping delvik cache... But does the galaxy s2 require checking of all of that unmounting/mounting?
heyitsmeyo2 said:
Okay, great! Glad it was so simple lol.
Now about my other question... Let me explain. When I would install a custom ROM on my sidekick, i remember having to do all sorts of things like unmount system/ unmount SD card before installing and remount them after (i dont remember the exact methods... Dont quote me on that).
I know the general procedure of basically Wiping data, Wiping cache, Wiping delvik cache... But does the galaxy s2 require checking of all of that unmounting/mounting?
Click to expand...
Click to collapse
Flashed many roms, and no need for all that. Just make sure you wait the 10 minutes after flashing a rom.
FlaShing roms on this phone is so simple "that even a caveman can do it". I would also advise to ditch clockwork recovery and install twrp, also never use rom manager to flash roms. Just follow the op's instructions on what steps to follow to flash the rom successfully. Also no need to mount and unmount anything. Good luck.
Awesome! Thank you all for your replies, glad to here that flashing is much simpler on this phone
I really wouldnt recommend anyone rooting a sidekick as a beginner. It was my phone, i soft bricked ot my first time. Ugh, it was such a hassle! And it left me a little traumatized to try anything on this. lol!
Thanks for all the help!
Here are the genreric steps to follow to flash a rom (and yes, TWRP is recommended instead of CWM):
- place the rom zip on the internal storage
- place a copy of the radio zip that you have on the internat storage (for safety reasons)
- copy Google Apps zip if it is not included in the rom (most roms do not have these included, but the dev might provide a tuned version)
- reboot phone and enter the recovery menu (hold vol up + vol down pressed while booting)
# In recovery mode
- wipe data
- wipe system
-(Use Darkside Super wipe if still on cwm 5.0.2.7 or below)
- flash rom
- flash gapps (if missing from the rom)
- wipe cache/ dalvik cache.
- reboot and wait 10 mins
- reboot and wait 1 minute
- enjoy
If you are planning on flashing a Rom on your phone of course twrp recommended and you should definitely try Jedi mind trick x2 for the t989 Hercules. It is the most stable Rom on the Samsung galaxy s2 T989 T-Mobile. The instructions above are the best instructions you should follow. And read it carefully or you will brick your device. If using twrp follow the twrp method. And if using cwm make sure you use the extra cwm steps. It is super important you follow them unless you want a fancy paper weight.
Sent from my SGH-T989 using xda premium
I just flashed my phone last night to the Liquid smooth rc 9. This was my first root and flash. I used titanium backup for the apps, used ROM manager to flash to the latest cwm. Here is a link I used
http://forum.xda-developers.com/showthread.php?t=1926754
Great instructions! Good luck!
Sent from my SGH-T989 using xda app-developers app
TomThom said:
I just flashed my phone last night to the Liquid smooth rc 9. This was my first root and flash. I used titanium backup for the apps, used ROM manager to flash to the latest cwm. Here is a link I used
http://forum.xda-developers.com/showthread.php?t=1926754
Great instructions! Good luck!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
You have it all wrong. Use twrp and use app 2 zip
Sent from my SGH-T989 using xda premium
How many times can a person wipe everthing and flash new roms before it starts to cause problems with your phone if it even does thanks
Sent from my SPH-L900 using xda premium
sliverr7x said:
How many times can a person wipe everthing and flash new roms before it starts to cause problems with your phone if it even does thanks
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I think as long as you do a FULL wipe between flashes (system, data, cache, dalvik cache) there is very little risk of screwing something up. Assuming you flash the compatible rom for your device. That said, I flash stuff constantly without doing a full wipe, and occasionally things pop up, but I havent had anything that caused anything major, YET. And I dont make any complaints if I do run into issues, I consider it my fault for not Full wiping first. Anyway, I think most would tell you to do a full wipe before flashing a new Rom or major update, unless you are just flashing an update of the current rom you are on. I flashed about 6 times yesterday back to back, only wiping dalvik and cache, and had no issues. The developers dont like to hear about issues if you haven't done a full wipe before flashing, and rightly so. They dont want to waste their time chasing issues that may only be caused because something leftover from a previous rom is jacking up your install of their rom / work. Hope that helps....
So, I say flash away, you'll be addicted in no time!!
1. Research, know what you are flashing.
2. Nandroid back up before flashing.
3. Wipe,( or at least follow the reccomendations from the developer) FULL wipes are highly recommended IMO.
4. Flash away!
5. Thank developers
6. Repeat!
If I've left something out please correct it....
If you're speaking of a hardware failure, I'd start worrying after wiping/flashing a rom everyday for 5 years straight. Provided you don't have an existing hardware issue, you should be okay.
Sent from my SPH-L900