[Help] defy stuck in motorola logo

[ehsan_yany]

Hello guys, one of my friends was trying to install the cyanogen for first time but after flashing 2.2 it stucked in M logo! and the buttery is unknown ( there is a question mark on the battery logo when he plugs in the charger). he tryed to flash some other ROMs (official 2.2 and other 2.2) but every time there is same problem and just M logo!!!
what can he do? please help... i will really appreciate your help!

 

[Cristi_10]

seems that your battery is too low on power to flash a sfb so you can try http://forum.xda-developers.com/showthread.php?t=892026 see if it works

 

[Cacceli]

Hello guys, one of my friends was trying to install the cyanogen for first time but after flashing 2.2 it stucked in M logo! and the buttery is unknown ( there is a question mark on the battery logo when he plugs in the charger). he tryed to flash some other ROMs (official 2.2 and other 2.2) but every time there is same problem and just M logo!!!
what can he do? please help... i will really appreciate your help!

Try to flash another rom or backup if you get to recovery mode.

 

[juli9797]

Delete the Cache and Dalvik cache via 2ndinit.

Sorry for my bad English!
Julian

 

[5starfish]

did you double wipe?

 

[ryan8r]

Wipe data/cache using stock recovery, Flash full SBF.

Sent from my ME525+ using Tapatalk

 

[ehsan_yany]

thanks everyone. we wiped data / catche / dalvic and everything! for more than 5 times!!! but the M logo is still the only thing we can see after flashing several ROMs via RSD Lite...

 

[farsight73]

Sometimes the sequence of flashing is vital to make it right.

I think you need to perfom full wipe follow with flashing new sbf. And talking about sbf, there's some img version of which won't work from higher to lower (sort of downgrading) regardless of the sbf you're using. You must need sbf file of the same img version or higher for the flashing process to success. To get this right, you must know exactly your original rom or sbf you were using.

2ndly your rsdlite might be the culprit here too as some run the flash but never pass or failed at bootup due to incompatible rsdlite version and configurations.