egzthunder1 · Sep 24, 2012 at 11:00 am

Defy Flashing Gone Wrong? Solve it with Ease

The Motorola Defy: a phone that, much as its name suggests, should be able to withstand elemental rage. When it came out last year, lots of blogs and websites showed how the Defy was impervious to submersion by dumping it in a cup of water. This resulted in the feeling of complete and absolute immunity, with many touting the device as “immortal.” However, as with most “immortal” characters of virtually every story, there is always something to which they are vulnerable.

In the case of mobile devices. and in particular that of the Defy, the Achilles’ Heel is the flashing custom ROMs. It is really no surprise that this is the case, as many Motorola devices have had a set of complications when it comes to flashing unsigned code. If you happened to hit the “weak spot” by mistake and bricked your device while trying to flash it, XDA Forum Member rtk217 has a guide to bring it back from the dead.

The guide goes into very minute detail as to what you need to flash, and in what order. The dev has provided tons of resources as well such as direct links to the files needed, alternatives to options that may require extra hardware, and a lot more. Needless to say, a device can be bricked for a multitude of reasons, and the level of bricking could range from partial to completely unrecoverable. All in all, this may or may not work for you based on your actual situation, but if you are already bricked without a clue as to what to do, you really have nothing to lose. What are you going to do? Brick it more?

Having said this, please do proceed with care and read the entire guide before attempting to get started. Make sure that all the files were downloaded successfully by checking the md5sum against the download source to ensure that you are not trying to flash corrupted files onto your boot partitions. Leave some feedback for the dev if this guide helped you in any way.

I tryed to flash custom 2.3.6 fixed sbf.
which didnt end well, after powerup i would go straight to bootloader with err codes.

You can find more information in the guide thread.

Want something published in the Portal? Contact any News Writer.


_________
Want something on the XDA Portal? Send us a tip!

egzthunder1

egzthunder1 is an editor on XDA-Developers, the largest community for Android users. I have been an active member of xda-developers since 2005 and have gone through various roles in my time here. I am Former Portal Administrator, and currently part of the administrator team while maintaining my writer status for the portal. In real life, I am a Chemical Engineer turned Realtor in the Miami area. View egzthunder1's posts and articles here.
Mario Tomás Serrafero · Jul 31, 2015 at 11:00 am · no comments

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of the biggest flagship lines issue their latest iterations. Phones like the LG G4 and Galaxy S6 were some of the most anticipated devices in smartphone history, and the hype surrounding the M9 and OnePlus 2 had us discussing for weeks. But for the most part, the awe has vanished.   There is a feeling that virtually all of us at the XDA office...

XDA NEWS
Jimmy McGee · Jul 31, 2015 at 06:00 am · 1 comment

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is covered by Jordan when he reviews all the important stories from this week. Included in this week's news is the announcement of a serious security vulnerability on Android and be sure to check out the article talking about how easy it is to make your one Xposed Module. That's not all that's covered in today's video! Jordan talks about the other videos released this week on XDA...

XDA NEWS
Mario Tomás Serrafero · Jul 30, 2015 at 02:04 pm · 3 comments

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising developments and it being natively supported on Android M, we can soon expect to see them on smartphones everywhere. If done right, it is a useful feature that allows for quick unlocking and authorization. There are concerns regarding security, but nonetheless the industry seems to be embracing it with open arms. What do you think?

DISCUSS