Database Users

[Q] Defy bricked - any hope?

Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading

The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.

Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice

ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium

nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.

I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk

I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.

what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium

When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.

Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk

I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate

Is the general consensus that this is an unfixable hardware issue, then?

Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow

[Q] Defy can't wipe data/cache, can't do factory reset, can't flash sbf.

Hello,
for last few weeks I have a problem with my Defy, apps crashes, wifi connection drops, phone calls drops etc.
I tried to do factory reset, but it restart exactly as before - nothing has been reset.
When I go to recovery mode and do wipe data/cache, nothing has been deleted. It says the wipe has been done, but when I restart the phone it looks like untouched.
I've tried to flash it with exactly the same sbf, but I got the "Error verifying Code Group 33,34,35 etc checksums", I've tied different sbf, bit all shows the same errors with checkums. After that the Android does not start, Defy turns on and all I can see it the bootloader screen and the message "code corrupt".
What is strange, if I don't touch the phone for a day or two than... i can turn it on with Android system starting as it never has been touched, nothing erased, but again wipe data/cache, factory reset, new/the same sbf - nothing works.
Looks like the data on the phone has been locked and there is no way to delete it.
Anyone know to to fix it?

Please ask all questions in the Q&A section. Thread moved there.

First write what ROM you have on the defy ?
Try put battery out for a 10 min ,when you turn on phone and you see blue led push vol- and there is recovery and there try do wipe's
if not works ,try use RDSLite and flash stock ROM once again (have to download stock ROM from forum ,look for it)

slon11 said:
First write what ROM you have on the defy ?
Click to expand...
Click to collapse
Defy+_4.5.1-134_DFP-125_(2.3.5)_CEE_(PL)
slon11 said:
Try put battery out for a 10 min ,when you turn on phone and you see blue led push vol- and there is recovery and there try do wipe's
if not works ,try use RDSLite and flash stock ROM once again (have to download stock ROM from forum ,look for it)
Click to expand...
Click to collapse
I do wipes, but nothing wipes out. After I wipe data and cache the phone turns on as nothing has been wipe out :/
RDSLite no matter what rom I use always says the error of checksums...
I tried to run a zip file from recovery, but says always something about "failed to verify signature" etc.
Any ideas?

Did you root you phone ?? If you did sth could went wrong with bootloader. Try make root once again. If you didn't make root ,just make it and tray flash CM10 by Quarks new kernel ,you will enjoy defy what you've never seen

Try a wipe from stock recovery, an sbf with ti blank flash option checked. If not then it looks like a hardware nand problem
Sent from my MB526 using xda premium

I'm having the exact same problem,did you get the phone to work again so far ?

Similar problem here also with a Galaxy Tab 10.1 wifi.

[Q] Defy Bricked. Really bricked.

- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899​(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.​I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.

There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?

if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature

I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense

Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf

Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.

vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions

corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?

First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all

I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)

vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see

corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D

UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?

vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting

corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.

vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life

corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.

vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above

Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas

@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7

Brick Defy

Good afternoon,
I'm a new user of this fantastic site; I come from Italy and some days ago I bought a new Motorola Defy red Bayer lens, a smartphone that I like a lot.
Yesterday I decided to flash the GingerSpeed v1.2 rom, but I probably bricked it...
What I made:
1. Flash with RSD Lite the Nordic Froyo (I started by Vodafone Froyo);
2. Root with SuperOneClick and install recovery with 2ndInitDefy 2.3;
3. Wipe data, wipe cache and wipe dalvik cache from custom recovery;
4. Advanced restore --> System and then data;
5. I wiped again, but I thought that I deleted the data restored on 4 point, so I restored again the data;
6. I wiped only cache and Dalvik cache, I flashed the 4.5.3-109DPP-11 kernel and wiped again the two caches;
7. I flashed ADW Launcher, than I rebooted;
8. The system actually started and I saw the first screen of the rom that said to insert the SIM;
9. I powered off the device, pull out the battery, insered the sim card, put on the battery and it didn't powered on! :crying:
So what I obtained was a device that didn't power on and so didn't enter in bootloader or recovery mod. If I plugged it on PC this doesn't recognize the phone, that was dead... To obatin white led I had to press volume+ button, put on the battery, press power button, release the second one, then the first one and plug it to the PC, but RSD Lite still didn't recognize it...
I tried all the method that I read on the web: try to enter in BL mode after plug in, before plug in, with and without the battery, trying with a lot of version of RSD Lite, but it is the same...
So I charged to 100% my battery with another Defy and now it doesn't show the permanent white led, but only for one moment (like a fast flash); sometimes it doesn't show even the "flash". What doesn't change is that the phone is still dead, and I can't make the PC recognize it...
I think that if I can make RSD Lite recognise the phone and then flash an original SBF it will return to live, but I can't make this... :crying:
There is someone that can help me, please? I will be forever grateful!!!
Thank you so much, and sorry for my english.
Good afternoon.

You could try to connect it to another PC to see if it gets recognized. Supposed you tried suggestions from this thread.
There's nothing wrong with your English.

I can't go to recovery or bootloader mode, it is actually dead!
I also tried the McGyver hack, but it seems to be indifferent; still a little white flash when I connect the USB and can't go to the bootloader mode.
Motorola Italy closed its door, so I can't send it to repair... :crying:

You don't need McGyver method 'cause your battery is fully charged. See this thread, think it's a similar issue. Looks like even though you can't go into the bootloader, RSD can recognize your phone as connected.

THIS is the problem! Even if the battery is fully charged RSD doesn't recognize my phone...
I tried to connect it with Power + Vol+, only Power, without buttons... but RSD still doesn't recognize my phone and the white led make a little flash.
I think that the PC is ok; RSD recognize without problems another Defy...

You had a working defy before you inserted SIM card. Guess you already tried it but, try to power on without SIM and sd card. Otherwise it's a hardware issue after all.

It's the first thing I made...
There aren't any other solutions? Motorola Italy closed its door and I don't want to put in the trash my Defy, it is pretty new! :crying:

Ok, I found a Motorola service center in my town, so I sended my Defy to repair...
Hope that they don't see that it is rooted and that they can restore it without opening or change with a refurbished one...

Andrea45 said:
Ok, I found a Motorola service center in my town, so I sended my Defy to repair...
Hope that they don't see that it is rooted and that they can restore it without opening or change with a refurbished one...
Click to expand...
Click to collapse
My wilde guess that this is a motherboard issue. Doesn't matter as far as you can get a working defy back :fingers-crossed:

Don't Worry
Andrea45 said:
Good afternoon,
I'm a new user of this fantastic site; I come from Italy and some days ago I bought a new Motorola Defy red Bayer lens, a smartphone that I like a lot.
Yesterday I decided to flash the GingerSpeed v1.2 rom, but I probably bricked it...
What I made:
1. Flash with RSD Lite the Nordic Froyo (I started by Vodafone Froyo);
2. Root with SuperOneClick and install recovery with 2ndInitDefy 2.3;
3. Wipe data, wipe cache and wipe dalvik cache from custom recovery;
4. Advanced restore --> System and then data;
5. I wiped again, but I thought that I deleted the data restored on 4 point, so I restored again the data;
6. I wiped only cache and Dalvik cache, I flashed the 4.5.3-109DPP-11 kernel and wiped again the two caches;
7. I flashed ADW Launcher, than I rebooted;
8. The system actually started and I saw the first screen of the rom that said to insert the SIM;
9. I powered off the device, pull out the battery, insered the sim card, put on the battery and it didn't powered on! :crying:
So what I obtained was a device that didn't power on and so didn't enter in bootloader or recovery mod. If I plugged it on PC this doesn't recognize the phone, that was dead... To obatin white led I had to press volume+ button, put on the battery, press power button, release the second one, then the first one and plug it to the PC, but RSD Lite still didn't recognize it...
I tried all the method that I read on the web: try to enter in BL mode after plug in, before plug in, with and without the battery, trying with a lot of version of RSD Lite, but it is the same...
So I charged to 100% my battery with another Defy and now it doesn't show the permanent white led, but only for one moment (like a fast flash); sometimes it doesn't show even the "flash". What doesn't change is that the phone is still dead, and I can't make the PC recognize it...
I think that if I can make RSD Lite recognise the phone and then flash an original SBF it will return to live, but I can't make this... :crying:
There is someone that can help me, please? I will be forever grateful!!!
Thank you so much, and sorry for my english.
Good afternoon.
Click to expand...
Click to collapse
Don't Worry, defy is very hard to brick as its bootloader is locked..try flashing sbf
Things that you may have not noticed:-
1) Proper procedure to get into bootloader i.e. Power+Volup (swiched off mode)
2) Install proper moto drivers in your PC..so that it recognizes your phone.
go to this thread:-
http://forum.xda-developers.com/showthread.php?t=966537

@nilesg19: I know, but I bricked it...
@Vicsa: Yes... Thank you for all your help!
I have a question: there are some tricks and/or advices to NOT brick the Defy while flashing or messing up with rom?
Now, I know that is forbidden to open a thread for ask which is the best rom, so I ask here.
1. Which is the best rom for cellular side (audio, speaker and microphone quality, 2G - 3G - WiFi reception, ...)?
2. Which is the best rom for stability, smooth and battery life?
3. Which is the best rom for camera side (photos, videos and audio quality)?
4. Which is the best rom for performances in the heavy games?

I'm glad that all went well. My advice: try to avoid RSD lite this time (you don't need it anyway)
Root your phone with SuperOneClick and install 2nd-init 2.0 (2.3 are reported not to work properly by several users).
Make a nandroid backup so you can always go back if something goes wrong. From this point you can try different rom's and keep the one you like the most. Download one of the rom's made for your defy model (MB525 red lense right ) and install it from custom recovery. Have fun

Ok, I find the problem... I used 2nd-init 2.3, probably it was the reason of the damned brick...
However, I must return to stock rom every time I want to try a new modded one to have a clean installation, mustn't I?
Also I read that some stock roms are better as base for the modded rom, so I flashed the Nordic one before the brick...
P.S.: If someone can give me some advices for the rom as I asked in the last post I'll have an idea when get back my Defy.

You don't have to go back to stock ROM every time you try some other ROM, you just have to wipe data and caches threw custom recovery if you want to install another ROM. You could try CM7.2 and skip step one cause you have froyo already.MS2GINGER is also a good stable ROM. CM10 is OK but have some minor bugs. Make a nandroid so you can easily switch between roms if you want to.

Even if I have to restore the system backup of the rom (for example MS2Ginger or GingerSpeed) or downgrade to GB (CM7) from ICS/JB (CM9/10) I don't have to go back to stock ROM?
Should I wipe data and caches after the flash/backup of a new rom or is it useless/harmful?
However, what do you think of Wiui ROM? It has the HD video recording like MS2Ginger and the stabilty and speed like CM7.2.

You don't have to ever go back to the original stock rom if you don't want to. You can wipe caches any time you like, can do no harm.
You must always wipe caches (including dalvik cache) before install, otherwise it just won't work. It is important that if you want to install a completely different rom to wipe everything you can wipe (including data) before you install it! Wiping caches afterwards is done for good measure and as I mentioned before can do no harm. If you make nandroids, just wipe everything BEFORE you want to recover one of them, that's all. Nandroid backup is actually your recovery in case something goes wrong, that's why it's so important to make one before you want to try some other rom.
As far as I know CM7 and MS2Ginger have a good battery life. Dunno about wiui cause I never used it. I'd say, just give it a try and see it for yourself.

Ok, I only have other two questions (I know I am annoying, but after the brick I'll be sure in the future).
After the flash of a new rom I can only wipe the caches and not the data because it is useless, right?
Before a Nandroid I must wipe data and caches but not after (if I wipe data it will erase the data backup that I restored some moments earlier, and wiping the caches is useless)?

Answer to both of your questions is yes. Just do the following if you want to install a rom of your choice:
1. Root your phone
2. Install 2nd-init
3. Backup all in custom recovery (aka nandroid backup) - it's going to be automatically stored in 'clockworkmod' folder on your sd-card
4. Wipe everything (data and caches) - N. B. dalvik cache is in "advanced" menu
5. Install rom (usually from zip file if its not a nandroid backup)
In some cases you have to flash another (gingerbread) kernel to make it work
6. Wipe caches for good measure (not data )
7. Reboot and enjoy your new rom
If something in this process goes wrong (what I doubt), wipe everything, restore your nandroid backup and reboot back to your stock rom.
As you can see you don't need to flash an SBF file with RSD lite, because you can do anything you want through CWM on your phone, and it's much safer. Besides sbf is nothing more than an image of a (mostly stock) ROM. You can accidentally flash a corrupted or wrong sbf file, and that can give you a lot of troubles. In the other hand, nandroid backup is much safer.

Ok, I understood...
Thank you so much!

AGAIN!!!
I got my Defy back working, I tried to flash MS2Ginger (GB Kernel) but I had some problems so I tried Wiui (with GB Kernel) and then CM7.2 Stable...
Home button didn't work and phone was rebooting every minutes so I decided to flash the Italian Froyo SBF and... BRICK!
Now I can connect it to PC, it recognize the phone and I am able to flash every .sbf I want but Defy is dead and doesn't reboot after the flash...
I know I'm very denied, but please help me to rescue my Defy!
EDIT: I luckily solved... If someone need the solution I flashed the Froyo 2.2.2 CEE and I got bootloop, so I wiped data and cache in stock recovery and now I have a working Defy!

[HELP] Bricked My U8800 [15Feb2013 Update]

Now, I dont usually open threads, but I have an issue here. I've searched and read a lot on how to recover the U8800 in case its soft-bricked, but I've tried the reflashing 2.2 method (Fails in about 5 seconds), Linux method (blefish's method, buzzcomp's method could not yield any results. I connected the phone in the bootloader mode (pink screen) to a Linux PC, but it doesnt appear as a new device there.
Then I tried to upgrade to 2.3, it installs fine, automatically enters recovery (formats data, cache etc), reboots a lot of times (bootloop?). So now whenever I on my phone, the Huawei logo just keeps flashing.
I've also tried to replace the files when connected in the pink screen by replacing the boot.img , recovery.img, amss.bin , EMMCBOOT.mbn file, yet it bootloops.
Prior to this, I had downgraded from Aurora to the stock 2.2, which worked fine. Then I replaced the stock recovery with CWM (the correct one, not the U8800 Pro's). I did the usual clearing of cache, data, formatted system, wiped dalvik cache in order for me to upgrade to a new ROM. Everything went downhill from there
UPDATE : I managed to get 2.3 to be installed. But everytime I enable "USB Debugging", upon the next reboot, there will be a lot of apps which closes unexpectedly, like the Huawei Launcher, Google Framework etc etc. I've tried B526 and B528, but everytime I have "USB Debugging" enabled, this happens. It works fine on 2.2 though
UPDATE 2 : After my fresh installation of the official 2.3, I'd changed the launcher to Holo Launcher, but it fails at starting up. If it does, it keep saying that Holo launcher has closed unexpectedly. The only way to fix it is to boot into recovery and wipe data.
Any help?

bump

U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium

yusopa said:
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Where can i find the stock partition flash file?

I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....

I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
Click to expand...
Click to collapse
hey i have this same mistake, i have the first boot fine after installing the official rom, but when i reboot the phone in normal boot (diisable fastboot) the phone gets bootloop, so i can't root it in order to put a new rom. i've downgrade to 2.2 froyo and get sum errors after installation but seems to work fine with 2.2 (can even root and install cwm).
after this i try again to upgrade to 2.3 official gingerbread, fist boot is fine, but when i reboot i get again stuck in bootloop... pls help

I am having the exact same issue, does anyone know how to fix this?

The problem is solved？

zgulia22 said:
The problem is solved？
Click to expand...
Click to collapse
I dont know for sure. I flashed another B528, same issues. Tons of FC messages.
I flashed an older B517, installed CWM, flashed DZO's excellent Aurora 5.0, and everything seems fine, for now.