Quote:
Originally Posted by Jaggu Poor guys they think its a hardware problem and replacing the motherboard, but do check if it will retain its water proofing once its opened up for parts replacement. |
@Jaggu: Thanks for the response. I didn't know this will be one more issue to sort out!! One of the strongest reason for me to go for Defy was for it's waterproof feature. . .How do I ensure that the service center people do it? I thought, authorized service centers will take care of all this by default

Yes, I am worried about their incompetence in identifying and fixing the firmware issue!!
Quote:
Originally Posted by S_U_N Sorry to hear about that.
Don't know what went wrong in your case, but I am planning to upgrade my completely stock Defy with 2.2.2 to 2.3.
I have a green lens so I guess official 2.3 will not work in my case, right?
I have faced several stability issues with 2.2.2 and I don't see 2.3 faring worse that that. Plus with Sygic (maps), the performance is bad - sometimes the phone takes several minutes to get back in control.
I am trying to trace the simplest set of instructions to do the upgrade.
I first want to backup everything that I have on the phone and card.
I assume I should root first and then do the backup, right? |
@S_U_N: Hope you got your answers by now from our valuable t-bhpians like phamilyman. . I suggest you to contact them when you are in the process of flashing your phone.
Quote:
Originally Posted by BaCkSeAtDrIVeR I suggest you should consider using a custom ROM. You have been using for real long time, so I guess there is no critical issues - PITAs, yes; but not real show stoppers.
I have not used Moto phones, but I guess at this stage, (if some kind of logo comes up), you can still try some other ROM / recovery image to salvage the phone. I suspect taking to the service center was your mistake #2. |
@BaCkSeAtDrIVeR: It was a bricked phone for me as I couldn't do anything further to bring it back to life (obviously due to my poor knowledge of the process. . .) I agree, if the animated Android logo was ON, it was alive.
I don't think it was my 2nd mistake!! considering the situation, that was the best option that I had as the phone is in warranty. . .but, those people are telling the same reason for over 12 days and I am not happy!!
Quote:
Originally Posted by Athani My guess is that your phone was not bricked at all. If you can get into recovery, the phone is not bricked. In fact, if the phone even responds to adb from the computer, it is not bricked. |
@Athani: I agree sir. But, I could not progress in bringing it back to life.
Quote:
Originally Posted by Bluengel180 Word of caution to every Android tinker out there.
NEVER downgrade.if you've flashed 2.3 NEVER try to go back to to 2.2.as gingerbread changes the bootloader and when you downgrade all you get is a brick  |
@Bluengel180: Thanks for the info. I was not aware of it. And as per phamilyman, it should not be an issue so, you experts need to tell us NooBs what is right.
Quote:
Originally Posted by phamilyman No yaar.
That is the exact problem with half information. You needed to do more homework. I have downgraded to UK Froyo.
Let me say this for those who will read it in the internet and get scared from HALF information:
CHINESE FROYO IS NOT RECOMMENDED. Alot of things don't work - stuff like FM Radio & Flashlight (it can permanently get off). Why did you use Chinese Froyo?
That said, in your case - did you wipe both cache and DATA as well? If the phone booted, it is NOT BRICKED. BRICK is when phone does NOT boot at all. Here is how I learned the hard way: xda-developers - View Single Post - [DEV][ROM] CyanogenMod 7.1.0 (Android 2.3.7) (my issue was solved over next 3-4 pages). I am quite sure that if your phone booted and showed android logo then it would have no issue. My problem was that my phone's down button" works in 2nd-init only if I press it 30% mid-way. In your case did you try reflashing? Did it enter recovery at all?
@Bluengel - Gingerbread on Defy uses the 2nd init - it DOES NOT REPLACE the bootloader by default IIRC. All "gingerbread" Defys for instance have Froyo with 2nd init operational that brings in GB from thereon. Only a few guys use the "leaked" GB ROM (or custom ROMs based on it) that itself have lots of problems.
@BSD: Boss, EVERY manufacturer's process is different. You cannot make one advice which works for all. 99.999% much more than meets the eye. General advise to all defy owners - before you guys have any such problems that warrants visiting the service center - please STOP & drop me a line. I should be able to help out in 99% of cases - having been there myself! Of course, I undertake no warranty for my advice!!
So for defy owners wanting to downgrade to official ROMs - the step is SIMPLE: - Reboot, enter recovery (on blue LED, press down)
- Wipe cache and then wipe data. wipe dalvik as well (advanced->dalvik)
- Go back to previous menu and switch off
- wait a few seconds (or maybe i'm superstitious) - then press up button and switch on. You will see the bootloader mode.
- Connect USB, and flash the SEA ROM or the UK ROM (what i use most often).
Reboot and enjoy. If there is a problem, ask here/PM me. or head over to the XDA thread here: [DEV][ROM] CyanogenMod 7.1.0 (Android 2.3.7) - xda-developers - you should get lovely knowledgeable real time help there. 99.9999% cases its near impossible to brick a Defy (in my experience). A bit of patience and xda wisdom should win the day.
Whitesquall,
If i were you, I would head over tomorrow to the service center, try and enter recovery or reflash the phone. "board having a problem" sounds like typical service center incompetence. if the phone booted enough to show android logo (and i'm assuming the logo was animated, right?) then i dont see where the board should develop an issue, honestly. |
@phamilyman: I am really happy and appreciate your enthusiasm to help fellow t-bhpians

. I did think of contacting you and held myself back coz I did not want to disturb you at odd hours (I did all this on Oct 31st night).
You are absolutely right in pointing out about doing enough homework. But, for me, the issue was different! Though I did lot of reading, I could not follow some of the writeups as the technicalities were beyond my understanding (I got confused with information overload!!). I tried and failed.
Yes, on a second thought, I should have contacted experts like you (I did not know your inclination to help others in odd hours).
Quote:
Originally Posted by phamilyman @Whitesquall- any update on your phone? Did u get time to go n try what I recommended? |
@phamilyman: I posted the story only after I handed over my phone to the service center. I am still wating for them to come back to me. . .I gave it to them on 2nd NOV. It's already 12 days!! God, please help!