Related
Hey guys,
so i was on a plane yestarday and obviously they want you to turn your phone off. I did so and when i landed i tried turning it back on but only to my surprise it would. Was just stuck at the White HTC screen and just kept resetting and doing the same.
Luckily I was able to get into the bootloader and reflash the rom and backup, however, its a pain in the butt to have to do so every time my phone shuts off or I have to shut it off.
Havent tried another custom rom yet, will do so shortly, but just wondering why this is happening? Any advice?
What rom were you on? And make sure to install with a clean install.
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
hasseye said:
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
Click to expand...
Click to collapse
You pretty much want to wipe everything but the sd card. So cache, data, dalvik, boot, and system. Then flash your rom and boot it up.
Sent from my hand with XDA Premium installed
I have this same problem with calks rom. Maybe try a different kernel?
Sent from my PC36100 using Tapatalk
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
hermanlf said:
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
Click to expand...
Click to collapse
I just don't understand why koush dosen't fix this and be done with it. I love that program... I use titanium backups dalvik cleaner anywho just saying that all
I'm having this sort of issue as well. I have wiped many times, gone back to stock, unrooted, even updated the hboot version. Has anyone figured out what exactly may cause this sort of boot loop? Sometimes, my phone just randomly reboots (even on stock default) and gets stuck in a boot loop.
Keeping the battery out for about 5 minutes allows it to boot back up, but I'm getting rather frustrated with it. I can't seem to pinpoint an exact issue. sometimes, it seems my battery is rather warm to the touch, sometimes, it's nice and cool. I've tried sense roms, non-sense, GB, and as I said earlier, stock RUU. Nothing I've done stops the reboots. I took it to the sprint store, and they saw nothing wrong with it. (Of course, it didn't reboot for them. Figures, eh?) I even got 2 alternate batteries. (One was the super big extended life)
Has anyone else had this same issue? I'm at a loss of where to go from here. I've poured over these forums, and the development forums for days. I never had this issue before...it's only started happening in the last week and a half. Keep thinking I must have missed something, but I'm not sure what.
I have some major issues!!!!
I have tried everything that I can think of and I still have problems!!! I have flashed several different radios, Different Kernals, Different ROMS ASOP and Stock and I don't know why my phone keeps restarting randomly! Sometimes it will go for an hour and sometimes it will go for 30 seconds but it keeps restarting itself. Currently I am running CM7 with the new GB Radio leak. Still happeneing please can someone help ease my frustration with this god forsaken phone! Thanks for any Suggestions!
Just a thought, are you undervolting your kernel at all? If undervolted too much mine has constant reboots.
All I can think of, but by no means am I an expert.
Are you wiping all partitions before flashing?
Full Wipe:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
Go into Mounts and Storage
3. Wipe System
4. Wipe Data
5. Wipe Cache
Go into Advanced
6. Wipe Dalvik Cache
7. Wipe Battery Stats
8. Install zip (ROM)
9. Power off/on, the boot back into recovery
10. Install zip (GApps)
11. Power off/on
*These are not my instructions. Saved them in evernote but I can't remember what thread it was from.
SD?
Had this same thing happen w/ a friend's DInc.
Copied all SD files to PC, removed and reformatted SD to FAT32, copied files back to SD, remounted, problem went away.
It was a guess on my part, and worked for her, idk if that was the issue, but the reboots stopped.
does it do it when you just install a rom with the stock kernal it comes with? Try running just 1 thing for a while to see what is causing it.
Or it may be a hardware issue.....you can search these threads for 'random reboots' and see that you may just need a new phone. I had the random reboots issue which originally lead me to rooting......which still didn't help. My problem started when I let the phone get way too hot on a car charger, does it seem heat related? Just a thought, would seem more likely than a kernel issue as every time you flash a new ROM you get a different kernel....
I had the same issue and had to get a replacement. Just make sure you put everything back to stock before you take it in. There is a great thread in develompement that will walk you through it. You may want to even try going back to stock anyway and see if the problem persists.
I can run stock everything and I still get the same problem I'm going to try and format my sd card and see if that works.....i don't know what else to do. And yes i have wiped everything before installing new ROM...
Sent from my ADR6400L using XDA Premium App
Problem with returning the phone is that I'm going to have to pay the hundred for insurance... Damn
Sent from my ADR6400L using XDA Premium App
FrierEM said:
Problem with returning the phone is that I'm going to have to pay the hundred for insurance... Damn
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I thought it was $50? and I also thought they ran out of Incs?
What I meant by back to stock is unroot, s-on, ect... You mentioned that you have tried different roms so I am assuming you are still rooted.
They are not out of incs, but if they were you would get an upgrade anyway.
Sent from my ADR6300 using XDA App
Now for about the last 2 months now this phone has been really getting to me. I have been putting different roms on my phones thinking that my roms have been messing up , but everytime i put a new rom on my phone i have the same issue. when i tried to log on the internet it will force close then i have to do it again to log online. it is really an issue now. does anyone know if it is my phoneor something? someone suggested that i got to rom manager and go to fix permission and i did that and it did not work. my ast resr s taking this root off my phone. the reason for that is because i am about to sell my phone and i dont want to sell it and the phone keeps having this issue. any suggestions?? thanks
May have to unroot and take to sprint, only thing I can think of
Sent from my Gruesomes Rom using xda premium
Trying switching your recovery to amon ra and I don't recommend using ROM manager instead flash your Rom manually in the recovery
Sent from my Gruesomes Rom using XDA App
well i doubt its anything sprint can do. i never had this issue before i believe its something thats on the phone from the root
nickhowell25 said:
well i doubt its anything sprint can do. i never had this issue before i believe its something thats on the phone from the root
Click to expand...
Click to collapse
Simply having root will not cause force close issues. It's more likely that you're either not wiping thoroughly, or that you're restoring system data.
Have you tried wiping everything (system, data, cache, dalvik, boot, sd-ext, and android_secure)? If you've been using ClockworkMod, you've probably only been wiping data, cache, and dalvik.
If this is the case, either switch to Amon Ra and wipe those before flashing, or use a wipe script that will wipe those options. Running an RUU may be another means to the same end.
If you've been wiping everything, or if it doesn't work, it could also be something with your radio. You can try updating or downgrading.
Sent from my Evo + MIUI using Tapatalk!
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.
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