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
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
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
Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?
Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.
The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.
mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)
mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.
mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA
Was it already rooted?
Sent from my SGH-T999 using xda premium
mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app
Love this ROM but trying to make sure that I have the latest version. When I look in about phone it shows my version to be 1.190..I have downloaded 1.275 and when I boot into recovery to flash it still shows the earlier version. What am I doing wrong?
Have you checked inside of the beanstalk thread ??
That would be the likely place for information regarding BS roms and updates. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Any luck yet? I too have BS (and love it!) And am looking to update it as well...this was my first ROM so I'm not necessarily sure how to update...do I just DL the new patch and just flash right over the version I'm running now?
Yep
Sent from my SAMSUNG-SGH-I317 using xda premium
Most beanstalk releases should be able to be dirty flashed overtop of previous installs. But just make sure that for one your recovery is up to date and that you wipe cache after the rom flash is complete. There is an option sitting to the left of the reboot button after you flash a file in TWRP. If this doesn't work you might have to do a full wipe and start fresh.
Personally I've done about 4 consecutive dirty flashes and it's been alright but you can honestly never really tell. It's always the safer bet to do a clean install where you wipe everything and flash the new update.
~PsyCl0ne
Sent from my GT-N7105 using xda app-developers app
Okay of course it was user error. I found that when I was going to flash to file I was not going to the correct file to choose from. I have to go into the 0 file and then scroll down the downloads in that file. From there I can choose the correct file. Since all this I have stumbled upon the Liquid Smooth ROM with Soap kernel and it is mind blowing. Battery life is crazy.
Sent from my GT-N7105 using xda app-developers app