Related
Since I have seen alot of individuals within ROM threads stating things such as, "Your ROM bricked my phone." or "I can't get your new ROM to install." decided to make this guide. Hopefully it will solve this issue and help educate people.
What not flasing correctly can do:
1. Cause your phone not to boot
2. Cause Force closes and issues
3. POSSIBLY Brick your phone (though I have not seen an Eris Brick yet)
We must also remember that:
1. The devs of these ROMs are NOT responsible for any damage to your phone
2. The devs spend alot of time with testing to make sure the ROM works.
3. A ROM will NOT always flash over a previous ROM
OK.. So onto the main topic..
assuming you are rooted and using AMON's Recovery. I suggest AMON's because Clockwork has had recent issues. Big thanks to AMON for this!
How to install a ROM properly:
1. Boot into recovery ( with either reboot to recovery option or powerdown and then holding volume up and power )
2. Goto Backup/Restore and do a NAND Back-Up
3. Do a data/factory wipe ( NOTE: if the dev says you can flash over an old version you dont NEED to do this, but if you don't do this and the ROM is not booting then I suggest you restart this process [minus the back-up] and do a data/factory wipe)
4. Do a Dalvik Wipe... 3 times (ALWAYS ALWAYS ALWAYS do this)
5. Flash ROM
6. Reboot and Wait ( after a Dalvik wipe and flashing ROMs first boot can take 3+ minutes to load... BE PATIENT )
More to Come...
If you could, please explain what a Dalvik flash does. Thanks in adavnce, and thanks for this thread. I've never had any issues flashing, but it's nice to see someone explain the basics....
MOS95B said:
If you could, please explain what a Dalvik flash does. Thanks in adavnce, and thanks for this thread. I've never had any issues flashing, but it's nice to see someone explain the basics....
Click to expand...
Click to collapse
"Dalvik cache is a program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the Dalvik-cache is the result of Dalvik doing a optimization of the running program." - Taken From Android forums
Basically it analyzes the phone before it boots. Then it sees what apps you have and will use and assigns cache to them. This way they will load quickly and properly.
When you flash a new ROM apps can change, or if you do a data/factory reset those apps are gone. SO wiping the Dalvik allows it to rebuild itself for what YOU are using.
This is also good to do after cleaning out or removing many unused apps from the phone. I usually do it once a week AT LEAST.
With the exception of a 2.1 ROM running apps2sd on an ext partition, is there really any point to wipe Dalvik if you have just done a wipe data/factory reset (which also wipes Dalvik cache)? And what exactly is the point of wiping Dalvik three times - why is once not enough? Is there something wrong with Amon Recovery which prevents a full Dalvik wipe unless you do it more than once?
It certainly doesn't hurt to wipe Dalvik after a wipe data/factory reset, but it should be already wiped.
I'm still fairly new, but I've flashed quite a bit. I didn't know to wipe dalvik x3. that's an interesting bit of info. Any reason why? Thanks
lp4261 said:
I'm still fairly new, but I've flashed quite a bit. I didn't know to wipe dalvik x3. that's an interesting bit of info. Any reason why? Thanks
Click to expand...
Click to collapse
Safety reasons... personally I do factory then dalvik 3x then factory again and dalvik 3x again.
Sent from my ERIS using XDA App
I tried this and now I have a paper weight lol j/k
tazzpatriot said:
I tried this and now I have a paper weight lol j/k
Click to expand...
Click to collapse
My plan worked
Sent from my ERIS using XDA App
I believe the reason is that sometimes even after a wipe people have reported residual data in the cache, I personally don't do it three times but I do a wipe, dalvik, dalvik, wipe.
Its not going to hurt anything and it gives me piece of mind.
Delvaris said:
I believe the reason is that sometimes even after a wipe people have reported residual data in the cache, I personally don't do it three times but I do a wipe, dalvik, dalvik, wipe.
Its not going to hurt anything and it gives me piece of mind.
Click to expand...
Click to collapse
cool. Thanks for the good info.
x3? I do once before and once after. Frankly once before has been enough for me... though I suppose being safe has never hurt.
If the dalvik cache still won't clear after 3 times you can piss on your phone. That seems to really help.
in most cases once is enough but like I said, it's not likely to hurt anything to give it a couple of wipes to make sure all the junk data is cleared.
Let me put it this way...
I wont use a public toilet just by seeing it is clean... ill clean it like twice ...
This is why I dalvik 3 times lol
Sent from my ERIS using XDA App
icbeer said:
If the dalvik cache still won't clear after 3 times you can piss on your phone. That seems to really help.
Click to expand...
Click to collapse
I tried that today.. now my phone wont turn on... any fix?...
Jk
Sent from my ERIS using XDA App
It would be interesting for someone like Amon to comment on the need to wipe data or recovery more than one time. In my opinion, once is enough. I'm 100% confident than wipes #2, #3, and so on are wiping blank space...
hallstevenson said:
It would be interesting for someone like Amon to comment on the need to wipe data or recovery more than one time. In my opinion, once is enough. I'm 100% confident than wipes #2, #3, and so on are wiping blank space...
Click to expand...
Click to collapse
I personally and others have experienced residual data... so is three too much... maybe... but its safe... two might be a better choice... this guide was made to make sure you have no issues... therefore I said three times for safety... if you want to just do it once... be my guest
Sent from my ERIS using XDA App
At the risk sounding like an idiot, I must ask this:
You mention wiping the Dalvik once a week. When you do this wipe, do you replace it (flash) something over it? Or can you simply wipe then reboot.
Sent from my FroyoEris using XDA App
J&M said:
At the risk sounding like an idiot, I must ask this:
You mention wiping the Dalvik once a week. When you do this wipe, do you replace it (flash) something over it? Or can you simply wipe then reboot.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Yep, just wipe and boot. After wiping dalvik, it will redo your app tree or configuration if you will, just clears all the current info and rebuilds it fresh.
Great thread, people still need it I guess
workshed said:
Yep, just wipe and boot. After wiping dalvik, it will redo your app tree or configuration if you will, just clears all the current info and rebuilds it fresh.
Great thread, people still need it I guess
Click to expand...
Click to collapse
Lol thanks buddy!
Sent from my ERIS using XDA App
if this is the wrong place for this SORRY IN ADVANCE
ok so after rooting my shift i followed all the steps got the recovery on there and downloaded a ROM and wiped everything and when the rom flashed it said error 7 instalation aborted so i hit reboot system now just to see what would happen because i did wipe everything so i was expecting to be stuck at the boot img..no problem was just playing around but the thing actually booted in a rom that looks 100% stock....what happened
even tho the ROM looks 100% stock it is def not i have adfree and esfile explorer added to app drawer now if its gonna flash the rom anyways why does cw 2.5.1 tell me its a no go with a stauts 7 i have even formatted my card to wipe it 100% and the same thing happens>?
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
RyteSyde said:
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
Click to expand...
Click to collapse
yeah it must have just been an issue with the rom i was flashing because i flashed another one no problem thanks for that bit of info though
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
JKILO said:
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
smoothtaste said:
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
Click to expand...
Click to collapse
Ok my fault...never took notice..thanks
Sent from my PG06100 using XDA App
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
HolyShift said:
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
Click to expand...
Click to collapse
Its good practice to always wipe. You may get by without it a few flashes. But eventually you'll be haunted by force closes, boot loops, etc.
Personally when I flash a new rom after the data, cache and dalvik wipes I format my boot, system, data and cache partitions manually via the mounts menu.
From experience, to truly see changes in rom updates or properly enjoy an entirely different one, this eliminates most problems before they ever manifest.
Sent from my Speedy Shift.
Wondering something here...when i wiped my device, i went thru rom manager and did the wipe device thing to wipe all user data to clear out CM7.0.
after that i installed virtuous to try it out, and i noticed in root explorer in the system>app folder, there were CM apk's in there. does virtuous use CM stuff in their roms?
if not, why would they show up even after a full wipe?
Also, has anyone here ever had issues changing from a non sense rom to a sense and back to non sense in a matter of 2 hours?
well, if they are any of the CM specific apps like:
CMparts or CMstats or CMwallpapers (I think there are a few more, can't remember off the top of my head), then it sounds like a case of a "format" that didn't actually format. you wouldn't be the first person to deal with this problem with rom mgr and CWM recovery.. it is known to be finnicky when it comes to formatting partitions (among other things ).
thankfully, we have a tool now that will give you a true, clean format of /system /data and /cache partitions without having to manually run the commands every time (like I know some of us have been doing).
if you are the kind of guy, like myself, who likes to perform a clean wipe between roms, I'd highly recommend downloading that and using it instead of the rom manager/CWM recovery options.
tackleberry said:
Also, has anyone here ever had issues changing from a non sense rom to a sense and back to non sense in a matter of 2 hours?
Click to expand...
Click to collapse
Can't answer your first question, but on my old Hero, I swapped from an AOSP ROM to a Sense ROM once almost every hour for a day because I couldn't make up my mind. Nothing bad happened to it and my father is using it now with no ill effects.
pmcqueen said:
well, if they are any of the CM specific apps like:
CMparts or CMstats or CMwallpapers (I think there are a few more, can't remember off the top of my head), then it sounds like a case of a "format" that didn't actually format. you wouldn't be the first person to deal with this problem with rom mgr and CWM recovery.. it is known to be finnicky when it comes to formatting partitions (among other things ).
thankfully, we have a tool now that will give you a true, clean format of /system /data and /cache partitions without having to manually run the commands every time (like I know some of us have been doing).
if you are the kind of guy, like myself, who likes to perform a clean wipe between roms, I'd highly recommend downloading that and using it instead of the rom manager/CWM recovery options.
Click to expand...
Click to collapse
yes i saw that program pop up when i was tying in the topic for this post! sounds like a great program wish it was posted a couple of days earlier lol. ill try when i get my device back.
wondering tho if these half ass wipes that CWM does caused my problems. i usually wipe when changing a type of rom, even with CM7 (nightly to RC for example). if i flash a nightly, i usually do a wipe every 2 nightlies.
Not sure what you mean by half ass wipes,lol, but I've never trusted the system wipe to do the job. I always do cache and dalvik along with it.
Sent from my HTC Vision using XDA App
enserio said:
Not sure what you mean by half ass wipes,lol, but I've never trusted the system wipe to do the job. I always do cache and dalvik along with it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i do too. half ass saying there is stuff not wiped lol
tackleberry said:
i do too. half ass saying there is stuff not wiped lol
Click to expand...
Click to collapse
Yeah... as amazing as CWM recovery is, the wipe process can be a bit.... lacking sometimes. If you don't use amazinglarry's superg2wipe script, then I would at least manually wipe through recovery before switching roms - this way you can be at least get most of the artifacts and "ghosts" left over from your last rom.
Sorry for bumping this old thread, I came across it while googling.
I've always used "wipe data/factory reset" in CWM. But that only wipes your /data and /cache partition.
Now, i only recently found out "wipe /system" under "mounts" in CWM. Meaning, I had never wiped my /system partition before, while swapping between 50 roms (be it AOSP or Sense). And I never had any problems. But the best way to fully wipe your system, is to do every partition manually + dalvik and battery stats.
Can anyone help me please, I have posted this on the PA thread but have had no response
I am unable to install PA on my nexus.
I have rooted and unlocked my device via the nexus root kit, downloaded the latest TWRP and installed this on my device. Moved PA and GAPPS to my storage and flashed PA first and then GAPPS, wiped dalvik and reboot the device. All that happens is the ROM doesnt appear to want to flash on the device as it reset my nexus back to factory settings but never installed the ROM.
I have also attempted this with goomanager but get stuck in a bootloop after install
However, I have been able to download and install CWM and CM10 so I know there is no issue with the device.
Can anyone provide any insight as to why this may be happenening
Have you verified the md5 of your download?
Also, patience is a virtue. Believer or not, some questions aren't always answered in mere minutes, as most folks have lives outside of the forum. I know waiting can seem unreasonable at times, but the timespan between you asking in the PA thread and then starting this completely new thread asking the same question was less than twenty minutes.
Sent from my Nexus 7 using Tapatalk HD
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Pirateghost said:
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Eagle1337 said:
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Click to expand...
Click to collapse
Wiping caches is unnecessary. New cache is built upon first boot.
You might have gotten away without wiping data if the bases for your ROMs were similar. Paranoid requires a wipe coming from most other ROMs.
Also you run the risk of corrupting your settings and app databases when you don't wipe data between different ROMs
Sent from my Galaxy Nexus
I could be wrong, but it seems that older versions of TWRP had the "wipe internal memory" option but it's not listed in TWRP 2.5's wipe advanced options. I have heard that wiping "data" essentially wipes internal storage, but I am certain that even after wiping, rebooting into recovery and wiping again, stiff is still on the sdcard0. Amazon mp3's for instance. Not a big deal, but if it's not wiping the amazon mp3's what else may it be missing on the wipe?
My specific issue is that I have heard that the bluetooth issue is fixed on many of the 4.2.2 roms now (aokp apparently included in this, although according to the guy bringing us aokp it always had "no issues that he knows of" since it's release), however after flashing the latest aokp, I am still experiencing random lockups and reboots while attempting to use bluetooth. In fact, 2 versions ago, the bluetooth seemingly locked up far less than it is with the latest aokp I've flashed. So I want to make sure everything is wiped (if that's necessary), before doing a fresh install of aokp in hopes of experiencing the bluetooth without issue.
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
RikRong said:
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
Thank you sir, I will give this a shot and let you know how it goes. Hopefully this will do the trick. You are a changed man, RikRong!
Sent from my Droid Razr M using xda app-developers app