Database Users

How to PROPERLY Flash a ROM

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

help phone keep restarting

hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!

kofpk said:
hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!
Click to expand...
Click to collapse
It sounds like you might have corrupted your recovery. You'll need to reflash it through rom manager, or through advanced if you can't get the phone to actually boot.
Sent from my HTC Glacier using XDA App

kofpk said:
hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!
Click to expand...
Click to collapse
jmwils3 said:
It sounds like you might have corrupted your recovery. You'll need to reflash it through rom manager, or through advanced if you can't get the phone to actually boot.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Although jmwils3 may be right to me it sounds like you have not Factory reset your phone through recovery, either that or you need to wipe your Dalvik cache and normal cache... personally I do a factory wipe through recovery twice and wipe norm cache and dalvik cache twice just to be safe. when you flash between roms and dont fully wipe, your phone retains some of the information from the previous rom which creates issues with the one you want to use.
try what I said, IMHO I think that's what is going on and not a corrupted Recovery as you were romming not flashing a new recovery

thanks
thanks for the reply... i reflashed the stock recovery.img and it work now.

kofpk said:
thanks for the reply... i reflashed the stock recovery.img and it work now.
Click to expand...
Click to collapse
Good to hear, bro
Sent from my HTC Glacier using XDA App

[Q] Reset back to stock ROM?
edit:
sorry having 25tabs can be confusing
Posted in wrong thread

Triketra said:
Although jmwils3 may be right to me it sounds like you have not Factory reset your phone through recovery, either that or you need to wipe your Dalvik cache and normal cache... personally I do a factory wipe through recovery twice and wipe norm cache and dalvik cache twice just to be safe. when you flash between roms and dont fully wipe, your phone retains some of the information from the previous rom which creates issues with the one you want to use.
try what I said, IMHO I think that's what is going on and not a corrupted Recovery as you were romming not flashing a new recovery
Click to expand...
Click to collapse
Little known fact learned from option94 wiping cache is wiping dalvik cache also
Sent from my HTC Glaciee using XDA Premium App

one u flash stock go get clockworkmod aka rom manager and install the newest recovery within the app. you should be able to download and restore any rom without bootloop.

Close please>?

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.

[GUIDE] Proper FULL wipe

I know this is not a development thread but I must insist we have something like this in this area. I would ask a mod to keep this sticky or maybe link to it from another sticky thread. I feel it's important to all development for accurate results and debug information.
I see this all the time. People think they are fully wiping when a developer asks for it. I believe that some people still don't understand what a full wipe is because there is no such single option in ClockWorkMod Recovery. Most likely the reason for that is because Koush didn't want too many posts about "I'm stuck on Google logo" or "my phone won't boot". So here is a test you can do yourself: Backup your ROM of course, and then do a full wipe. Then don't install anything and just reboot. If you end up pass the Google logo and onto the boot loop screen, then what you think is a full wipe is incorrect. If you are stuck on the Google logo and nothing is happening however, then congratulations... you know what you're doing
For the rest of you, here are proper steps to fully wipe without leaving any trace of ROM on your phone:
wipe data/factory reset
format /system
format /boot
Now most people think that the first option is enough. That may often be the case but because the developer can drastically change the contents of the /system folder, things can get messed up if you don't format it. And guess what, that first option will not do it. Wipe data/factory reset only wipes the /data folder which contains your personal settings and all the apps you installed. The ROM is then left blank as if you just flashed it and you can start over. FYI, the format of boot partition simply wipes the boot animation and you can restore it using the advance option in recovery from ROM to another.
I've seen some zip files which do this automatically so that's fine but at least you know what needs to be done to fully wipe.
There you go. I hope this clears some things. Now lets flash some ROMs!

Thank you
Sent from my Nexus S 4G using XDA App

Sticky please!

I follow the above wipe method for my Epic Touch 4G,SGSII, with the exception of flashing Calkulins Format All.zip at the very end and i havent experienced any issues yet. Hope i didnt just jinx myself...

Simple, yet I'm sure beginners miss it. I also vote for a sticky.

Isn't the dalvik cache stored in the /data partition?
Hence, factory reset necessarily wipes dalvik but wipe dalvik only wipes the dalvik portion of the data partition?
Sent from my Sammy Nexus 4G using XDA App

all we need is a zip that does all of that and were good!!
Sent from my Nexus S 4G using XDA App

no need to wipe when restoring?

Or use amonRA. Best recovery yet.
Sent from my Nexus S using Tapatalk

donsh00tmesanta said:
no need to wipe when restoring?
Click to expand...
Click to collapse
Nope, restoring will format each partition before it restores it.

+1 for sticky
This is one reason I like the cwm mods...all the wipe options are in one place

kdepro said:
Isn't the dalvik cache stored in the /data partition?
Hence, factory reset necessarily wipes dalvik but wipe dalvik only wipes the dalvik portion of the data partition?
Sent from my Sammy Nexus 4G using XDA App
Click to expand...
Click to collapse
Yeah. Forgot that its the case. Op edited. Only 3 steps now.

Hi I really like your thread!
Can I post a similar thread on the Vibrant forum? I'll give you credit!
Sent from my Surround.

Does anyone know the edify syntax off the top of their head to properly accomplish this? most of my attempts haven't seemed to work. would they all be formatted EMMC, even SDcard and system?

Or switch to a better recovery.
http://rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-download.html
Sent from my Nexus S 4G using Tapatalk

VeryCoolAlan said:
Hi I really like your thread!
Can I post a similar thread on the Vibrant forum? I'll give you credit!
Sent from my Surround.
Click to expand...
Click to collapse
No problem go ahead. The more people know the better.

pfer10 said:
Or switch to a better recovery.
http://rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-download.html
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I prefer kush's recovery. And this is a feature as far as I'm concerned. I usually don't do system format but when doing beta or alfa testing this is a must.

really2 good post man.. i've flash rom with full wipe as u said.. thanks a lot dude..
oICSv43 - *Matri1x* v13.0

Thanks. I never realized i should format the /boot. I have never done that.

Evo_Shift said:
Thanks. I never realized i should format the /boot. I have never done that.
Click to expand...
Click to collapse
Well technically you shouldn't have to but this thread is about a full wipe so to wipe any traces you need to wipe it.

Can't run Sense based ROMs

My wife and I both have MyTouch 4Gs and both of our phones exhibit this problem. Whenever I load a Sense based ROM both phones reboot without warning. The last time I had a Sense based ROM on her phone it would continuously reboot when plugged in to the charger. I loaded a Sense based ROM on my phone last night to try out and it would reboot every few minutes. I've probably tried six or seven different Sense based ROMs and the rebooting issue always happens. Both of our phones are currently running a CM7 based ROM and working fine. Anyone else see the same issue?

greenmaze said:
My wife and I both have MyTouch 4Gs and both of our phones exhibit this problem. Whenever I load a Sense based ROM both phones reboot without warning. The last time I had a Sense based ROM on her phone it would continuously reboot when plugged in to the charger. I loaded a Sense based ROM on my phone last night to try out and it would reboot every few minutes. I've probably tried six or seven different Sense based ROMs and the rebooting issue always happens. Both of our phones are currently running a CM7 based ROM and working fine. Anyone else see the same issue?
Click to expand...
Click to collapse
Did you verify the MD5SUM post pushing the ROM to the SD Card.

neidlinger said:
Did you verify the MD5SUM post pushing the ROM to the SD Card.
Click to expand...
Click to collapse
+1 this
And/or are you flashing anithing else right after flashing the rom? If you are, don't. Just flash the from and reboot. Also, make sure you're found a full complete wipe. Wiping data, cache and dalvik before flashing.
Sent from my HTC Glacier using xda premium

That problem can also be caused by the phone being overclocked a little too much. Try changing speed and voltage to match stock.
Sent from my HTC Glacier using xda premium

neidlinger said:
Did you verify the MD5SUM post pushing the ROM to the SD Card.
Click to expand...
Click to collapse
Yes, I verified this.
coupetastic-droid said:
And/or are you flashing anithing else right after flashing the rom? If you are, don't. Just flash the from and reboot. Also, make sure you're found a full complete wipe. Wiping data, cache and dalvik before flashing.
Click to expand...
Click to collapse
No, not flashing anything else. Yes, I wiped data, cache, and dalvik before flashing.
eqjunkie829 said:
That problem can also be caused by the phone being overclocked a little too much. Try changing speed and voltage to match stock.
Click to expand...
Click to collapse
I'm not sure what those ROMs were overclocked too, but I'm running CM7 at about 1209MHz right now and have no issues.

greenmaze said:
Yes, I verified this.
No, not flashing anything else. Yes, I wiped data, cache, and dalvik before flashing.
I'm not sure what those ROMs were overclocked too, but I'm running CM7 at about 1209MHz right now and have no issues.
Click to expand...
Click to collapse
You need to do a complete factory restore via the recovery image. the /system is the most important part to make sure is wiped. And from that statement you're not doing that.

neidlinger said:
You need to do a complete factory restore via the recovery image. the /system is the most important part to make sure is wiped. And from that statement you're not doing that.
Click to expand...
Click to collapse
Is a complete factory restore simply finding and flashing a stock image?

greenmaze said:
Is a complete factory restore simply finding and flashing a stock image?
Click to expand...
Click to collapse
No. Neidlinger is referring to a full wipe of /system /data and both caches prior to flashing a new rom.
Sent from my HTC Glacier using xda premium

greenmaze said:
Is a complete factory restore simply finding and flashing a stock image?
Click to expand...
Click to collapse
eqjunkie829 said:
No. Neidlinger is referring to a full wipe of /system /data and both caches prior to flashing a new rom.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
@EQJUNKIE829 hit the nail on the head. Just flashing a new OS isn't wiping the old one. You need to do a nandroid backup of your current OS, then do a complete factory reset. It WILL NOT wipe the recovery image or the hBoot. Then flash the new OS.

No matter how many threads I say to wipe the bloody system partition in, there is always this problem. Its frustrating.
Help my phone acts weird.
Did you do a full wipe?
Yes
Are you sure? You wiped the system partition?
Umm, I dunno. I think so.
:faceplam: Wipe system, data, cache and dalvik cache and reflash.
That fixed it. Thanks!
Sure thing! :hangs self:

estallings15 said:
No matter how many threads I say to wipe the bloody system partition in, there is always this problem. Its frustrating.
Help my phone acts weird.
Did you do a full wipe?
Yes
Are you sure? You wiped the system partition?
Umm, I dunno. I think so.
:faceplam: Wipe system, data, cache and dalvik cache and reflash.
That fixed it. Thanks!
Sure thing! :hangs self:
Click to expand...
Click to collapse
This person only has 5 post on XDA you could go a tad lighter.

neidlinger said:
This person only has 5 post on XDA you could go a tad lighter.
Click to expand...
Click to collapse
Oh no. I wasn't upset with them. Just in general. Its almost ALWAYS a wipe issue, and people just don't get it. I'm just griping period
Sent from my HTC Glacier using XDA App

Clean wipe before install and check md5um