• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

ROMs Things to avoid in CWM

MeowDude

Member
Hey just making a list from personal experience! (Also its 11:08pm and I'm bored ;) )

1) DONT EVER RENAME BACKUPS, EVER!!!
it mismatches the md5 sum, and CWM wont be able to restore it. I've done this before, trust me, crappy situation to be in.

2)NEVER WIPE YOUR SD CARD WHEN FLASHING ROMS!
not only does it suck *before* you wipe everything, its worse when its after you wipe everything, or worse, while wiping everything. Either way its, bye android 4.4, hello frustrating adb and sideload!

3)AVOID KEY TEST!
Just a basic annoyance. All it does is test to make sure VOL +/- and power are working. Worst part? You can't leave once it starts. Be prepared for battery pull.

4)DONT PREFORM BATTERY PULL, OR REMOVE SD CARD WHEN FLASHING, OR ESPECIALLY RESTORING BACK-UPS!
when flashing, due to it overwriting boot, you might get soft bricked, and in restore, due to it doing the same, but more severe, you could also softbrick your device. Easy to fix, but annoying.

5)DONT DO ANYTHING UNLESS YOU KNOW WHAT IT DOES.
from partitioning SD card to wipe SD card, there are many ways for us newbies to screw up, so follow guides closely, don't mess around, and you'll be find.

6)DONT FLASH THE INCORRECT ROM! [Thx Cyberdev!]
it will permanantly brick your device!

7)MAKE SURE BATTERY IS CHARGED BEFORE FLASHING ANY ROMS! [Thx Cyberdev!]
running out of power during flash = frustration and brick! (We could build houses out of these bricks! XD)

8 ) CERTAIN ROMS CANT HANDLE THE GAPPS BEING FLASHD NEXT!
some roms like surpreme emotion UI for fusion 2 have to reboot, then have the Gapps flashed seperatly. Otherwise it freezes at ATT logo FOREVER :eek:

9) MAKE SURE THE VERSION OF CWM/TWRP IS FOR YOUR DEVICE(thx CyberDev)
Having the wrong one can lead to bricking or worse! :eek:

10) UPDATE YOUR CR (CUSTOM RECOVERY) OFTEN (the CyberDev)
Some newer roms won't flash on older versions, and they are very buggy.

11) NEVER FLASH A BASEBAND, GAPPS PACKAGE, OR ROM THAT ISNT MEANT FOR YOUR DEVICE
Cant stress this more...most of us have tried CM installer, they're serious when they say to back off if your device isn't supported. It can also lead to Bricking or worse.

This was mostly common sense, but some of us have a lack of sense, PERIOD. Just burning time! :D l
Credit to Cyberdev for helping expand our list a bit more!
 
Last edited:
Omg i can agree on this list good job im a high experienced dev and this seems something i never csme across butbt teirs one thing missing

DONT FLASH THE INCORRECT ROM
will permenant brick your device


MAKE SURE BATTERY IS CHARGED BEFORE PERFORMING ANYKIND OF CHANGE OR ROM INSTALLATIONS
Will shoutdown and may soft or perm brick device

Also i did that before changed the backup name snd i was screwed but thought smart to fix it
 
Excellent document, MeowDude (and username, too! :))

You might also be interested in another thread we have in our FAQ section that's kind of related to this:


These sections relating to verifying your Nandroid backups, verifying any files that you download (i.e., check the MD5 or SHA1 sums), carefully follow the ROM dev's detailed instructions are probably most relevant to your thread here.

Cheers and thanks!
 
Heres another tip

DON'T INSTALL THE WRONG CWM
even though or cwm or twrp work the same, they dont have the same config as as any other phone has

MAKE SURE THE RECOVERY IS THE LATEST BEFORE PERFORMING ANY ACTIONS, OLDER VERSIONS ARE BUGGY!
everything has bugs be sure to check that your cwm ir twrp is up to date for your device sonetimes some operations may mess up at times due to bugs
 
Back
Top Bottom