I have to ask about the wiping thing.why do it and do I have to every time I flash roms or any thing else for that matter?
it gives you a clean foundation and people that know more than you recommend it.
If you don't wipe, remnants of the last rom will still be there, thus causing problems with the new rom if the framework for certain parts is different.
I'd recommend doing it all individually several times. I know that what most the guys do around here that flash with every nightly/beta that comes out. By doing it all independently, i mean by entering the mounts and storage part of recovery and format boot, system, data, cache multiple times.
I had issues with my camera for months because i wasn't formatting enough. And i was formatting using the general format in recovery but that just sometimes doesn't cut it.
There are also some tools that you can use that do a clean wipe for you 3 times. Wipeall is one i believe. Sometimes i use it but still do a manual once over to be sure. The time spent is worth it knowing that it can cause some funky problems.
Related
Dumb question, but how many .zips can you flash in the same recovery session? I have always flashed one at a time and with all of the wiping it tends to be quite time consuming.
Edit;;;
you're right... I had no clue... I apologize....
You can flash as many as you want (Mexigga, I'm honestly not sure what you're talking about ). The important thing to do is Clear your Cache and Dalvik Cache before flashing. Other than that, I've flashed a good 4-5 things before without any problems.
HOWEVER, if one of the things you flashes causes a problem you'll have to do them one at a time in order to determine which one is causing the problem.
Final word: ALWAYS NANDROID BACKUP. ALWAYS
You can flash as many as you want. Just wipe your cache and dalvik each time. Doing 1 at a time allows you determine which, if it happens, causes problems.
http://forum.xda-developers.com/showthread.php?p=23983384
Could this script be ported over? I'm not a dev by any means but I'd like this.
Sent from my Galaxy Nexus using XDA
It's not your butt. Wiping more than once doesn't do anything. Though, if someone can get me proof of a repeatable error that is only solved by wiping more than once before installing a ROM, I'll admit I'm wrong. As of right now, it's voodoo quackery from the people that insisted battery cache wiping was the sure way to double your battery life.
To clarify, this is distinct from wiping, flashing the ROM, and wiping again and re flashing the same ROM. Bad flashes seem to happen to me 10% of the time.
Just seems useful I personally wipe 2-3 times before a flash just to be safe. I've had bad flashes before I did haven't since.
Sent from my Galaxy Nexus using XDA
....
There is no possible thing that would change from wiping it once to wiping it 1000 times. A wipe wipes the data. Then it's gone. Wiping it again just wipes nothing. Remnants don't get left behind or anything. Have you ever tried deleting something twice? Same concept....
Peter
Its the same concept of a bad flash. You flash and have problems, yet re-wipe and flash again and it works fine. Sometimes when you do a wipe, for some reason or another every file doesnt get wiped. Its rare but it does happen. Wiping twice before flashing or just a safer practice. Sure if the file gets deleted, it cant be deleted again. But the issue at hand is that the file doesnt always get deleted. I used to sometimes have a bad flash with a ROM but ever since I started flashing twice before I install the ROM I havent had an issue. I dont think we get a bad flash because the ROM flashed bad, we get a bad flash cause files didnt get wiped and are left over from the old stuff.
EniGmA1987 said:
Its the same concept of a bad flash. You flash and have problems, yet re-wipe and flash again and it works fine. Sometimes when you do a wipe, for some reason or another every file doesnt get wiped. Its rare but it does happen. Wiping twice before flashing or just a safer practice. Sure if the file gets deleted, it cant be deleted again. But the issue at hand is that the file doesnt always get deleted. I used to sometimes have a bad flash with a ROM but ever since I started flashing twice before I install the ROM I havent had an issue. I dont think we get a bad flash because the ROM flashed bad, we get a bad flash cause files didnt get wiped and are left over from the old stuff.
Click to expand...
Click to collapse
Can you quantify this in any manner at all? Have you checked the partition to see what was left behind the first time and not the second? What was the file?
Out of curiosity, someone with a bit more android storage knowledge than me might be able to answer. Does wiping on android just 'uncatalogued' as most computer systems do and allow it to be written over, or is it an actually 'replace with 0'? Just kinda curious for my own knowledge.
Had a strange thing happen to me today with my Skyraider Zeus 1.3 ROM. Had everything setup the way I like but then I decided to try and change my lockscreen ring. Found some from somewhere, suppose to work with 2.3.4 sense 2.1. Flashed in recovery and restarted and got my status bar with icons but no lock ring or shortcut icons or any way to unlock it. So I pulled the battery, went in to bootloader, then recovery and did a backup restore. Everything was fine after that...for a while. Then i plugged it in to charge it, shut the phone off (all the way, not fast boot) to charge for about 30 minutes, then restarted. When it restarted, I had just a red battery icon, no percentage numbers just my red icon circle. Then i noticed when the screen would time out and dim, it would never shut off. It just stayed on dim, forever (and no, I wasn't plugged in). Restarted...same thing. Pulled bat...same thing. Finally I tried another restore of the same ROM, but it went right back to the recovery menu instantly without doing anything, then tried 2 more backups with the same result. Finally I did a completely different ROM restore and it worked. When it opened I noticed the battery icon was doing the same thing, along with the display eventually dimming and staying on dim. Did a complete wipe, data, cache and dalvik 3 times, flashed the ROM again figuring it would fix it... but no. After a few minutes, the battery icon turned red again and then the display would time out (after the 30 seconds i set), go to dim and just stay on. After awhile it went back to normal again but then did it again. This has happened about 4 times in the past 2 hours. I don't know what I did but its got me worried. Do you think it could be some settings file stored on my SD card? Or possibly the batterystats.bin file? I am about to reset it and see if that helps. Honestly, I don't know what is going on. I just hope its not hardware related. Its just coincidental that after my bad flash of the lockscreen ring that it happened, so i figured it was a software issue. Sorry so long guys, just in a bit of a panic right now
just do a full wipe and reflash the rom
casseer15 said:
just do a full wipe and reflash the rom
Click to expand...
Click to collapse
I did that. I wiped everything out 3 times just to make sure and reflashed the ROM, like I stated above. Strange though, I haven't seen the issue reappear since the first couple hours of my reflash, since then its been ok. I guess ill just wait and see if it starts to happen again.
Definition of Full Wipe
Just making sure you know what a full wipe is and allowing others to Search Full Wipe and know what it means. When I fist started flashing I wasn't quite sure what Full Wipe meant.
Here are the instructions:
In Clockwork Recover
scroll to mounts and storage
select format /system -> Yes - Format
---Done---
Select format /data -> Yes - Format
--Done--
Select format /cache-> Yes - Format
--Done--
Now you may flash a new rom
kwick85 said:
Just making sure you know what a full wipe is and allowing others to Search Full Wipe and know what it means. When I fist started flashing I wasn't quite sure what Full Wipe meant.
Here are the instructions:
In Clockwork Recover
scroll to mounts and storage
select format /system -> Yes - Format
---Done---
Select format /data -> Yes - Format
--Done--
Select format /cache-> Yes - Format
--Done--
Now you may flash a new rom
Click to expand...
Click to collapse
That is different from what I was doing. Though I am not new to flashing (almost a year) I have heard and read other posts through the months about people saying "do a full wipe" then saying "wipe data/factory reset wipe cache and dalvik cache". If this is the case there is a lot of people doing full wipes wrong. Hell I've even seen developers mention full wipes in this way. Not saying that your wrong, im just honestly not sure whats correct. But I am curious, what is the difference between the two? Is it because its formatting and the other is just wiping, or when its wiping is it also formatting at the same time? If that's the case wouldn't it be the same thing, just in a different way? You've peaked my curiosity
This isn't my list, but there are good explanations on the thread that I found, I cannot post the link due to my lack of postings but if you goolge: Full Wipe Spider
It should be the first search item.
Enjoy your new found knowledge.
Especially moving from Sense to AOSP, I format /system, /data, /cache. Usually, I do all three no matter.
I dont know but you could have problem with the battery or charger.
Let me start of by saying I am a Noob. I have been learning about the root and custom ROM process for about three weeks now. I have succesfully flashed the latest PacMan ROM and the latest SlimBean ROM. Both times I have reverted back to my Stock ROM. Everytime I flash a new ROM using TWRP, I wipe the Cache, Davlik Cache, do a Factory Reset, and Wipe the ROM. This leads me to believe I getting a clean flash, and everything seems to go smooth with the install. I have no problems with the inital boot, and it usually happens pretty quick.
I understand that each custom ROM has some great new features, but it hasn't out weighed that the battery life and speed (responsiveness) is still better on the Stock ROM. Is the reason I am seeing this is because the ROM's I have tried are 4.2.2 versus the stock 4.1.1? Is there something obvious that I am missing? If it appears that I am flashing correctly, is there a ROM that is should try the will improve me battery life and speed?
Thank you!
a full wipe also includes format /system.
how long are you using these roms before flashing back or trying a new one? the software takes a little time to settle in so if you're hopping onto a new rom every few days, you may not see the best that each rom has to offer you.
xBeerdroiDx said:
a full wipe also includes format /system.
how long are you using these roms before flashing back or trying a new one? the software takes a little time to settle in so if you're hopping onto a new rom every few days, you may not see the best that each rom has to offer you.
Click to expand...
Click to collapse
Do I format the internal memory of in TWRP? After doing some that is TWRP still functional? I have been afraid to do that because when I think of formatting it wipes everything. My thinking was the phone wouldn't operate.
Can you walk me through it in TWRP?
Thanks!
Huskerjeff said:
Do I format the internal memory of in TWRP? After doing some that is TWRP still functional? I have been afraid to do that because when I think of formatting it wipes everything. My thinking was the phone wouldn't operate.
Can you walk me through it in TWRP?
Thanks!
Click to expand...
Click to collapse
as long as your recovery is current, you have a backup (nandroid) and you have the ROM/gapps zips on the device, you're good to format (wipe) system. that erases the OS and allows for a new, clean install.
make a backup (if you dont have one)
wipe data/factory reset
wipe cache
wipe dalvik
wipe system
flash rom
flash gapps (if required)
reboot
let device sit a few minutes and reboot again.
Theres more to it then just flashing and having a better running phone. If that was it everyone and their mother would do it. You need to learn about the system and ROM you are operating on and tweak the settings to optimal performance for your phone, and more importantly to your liking.
Every phone is different. If one rom works great on one persons phone it may not run so good on another persons. You have to learn and have enough know how to be able to set the phone up in a way that runs good for you. While it may be frustrating at times I guarantee if you take the time to try out a couple different roms for a couple days at least, and play around with the settings until you know what they all do and why they are there and how work for or against your goals you will end up with a phone that you enjoy using on all levels. Features, performance, looks, etc.
Hope this helps, and good luck finding your custom rom 'sweet spot'
Try AxisM RLS18 rom its a great rom with so many features to it.
xBeerdroiDx said:
as long as your recovery is current, you have a backup (nandroid) and you have the ROM/gapps zips on the device, you're good to format (wipe) system. that erases the OS and allows for a new, clean install.
make a backup (if you dont have one)
wipe data/factory reset
wipe cache
wipe dalvik
wipe system
flash rom
flash gapps (if required)
reboot
let device sit a few minutes and reboot again.
Click to expand...
Click to collapse
TeknoGodz said:
Theres more to it then just flashing and having a better running phone. If that was it everyone and their mother would do it. You need to learn about the system and ROM you are operating on and tweak the settings to optimal performance for your phone, and more importantly to your liking.
Every phone is different. If one rom works great on one persons phone it may not run so good on another persons. You have to learn and have enough know how to be able to set the phone up in a way that runs good for you. While it may be frustrating at times I guarantee if you take the time to try out a couple different roms for a couple days at least, and play around with the settings until you know what they all do and why they are there and how work for or against your goals you will end up with a phone that you enjoy using on all levels. Features, performance, looks, etc.
Hope this helps, and good luck finding your custom rom 'sweet spot'
Click to expand...
Click to collapse
Update: I searched for a ROM using a 3.0 Kernel and found one with great battery life reviews call "Sons of Android". I installed it using TWRP 2.4.4 with the directions quoted above, and everything is great execpt for two things.
First, I always seem to get mirrored data. There is a Emulated folder and an SDcard0 folder that appear to have the same data. I have searched in the forums and found that it is an issue, but havent seen a solution.
Second, Netflix is draining the battery twice as fast as the stock 4.1.1. Before I could watch 45 minutes with 10% of battery and now the same 45 minutes is taking 20-25% of battery. Is this a 4.2.2 problem. It has been a problem on all the ROM's I have tried.
I am going to stick with this ROM for a while beacuse other than netflix the battery life is good. Just about the same as my stock ROM.
Thank you for all of your help for the Noob.
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g