Develop Bugs

[Q] Motorola defy bricked

Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie

What rom have you been using ? It looks like you have flashed 2.21 or 2.34 while you had had 2.51 before or you was trying to direct downgrade from 2.2 froyo to 2.1 eclair.

Use another sbf for the flash maybe that is the problem
Sent from my MB525 using Tapatalk

choudu1 said:
Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie
Click to expand...
Click to collapse
Make sure you use a compatible boot/devtree loader. Try the 2.1, the 2.51, and the Tmobile 3.4.2-107 available elsewhere on this board.
It's nearly impossible to brick the Defy.

Not to hi-jack the thread - just don't want to start another one for an identical issue. I am running into exactly the same problem though I have the USA version - not UK.
Here is what I did:
To start, I had the stock USA ROM (My wife has the same phone so I can get specific details on stock build after I get home from work, if needed)
1. Rooted with superoneclick
2. Installed Custom Recovery (http://forum.xda-developers.com/showthread.php?t=875233)
3. Installed Milestone Overclock & Overclocked
4. Made backup to my SD Card of current image (using SW from step 2)
5. (On PC) Installed RSD Lite
6. Downloaded 2.34.1 Central Europe ROM (.sbf) and copied into Prog. Files for RSD Lite. Device showed up in RSD Lite so I clicked “Start.” RSD Lite created image, then copied image over – phone display changed to saying “SW Loading” or something like that. When the load finished executing, the phone went to reboot and all I got was the same little white light (up by the presence sensor) that was on steady for the phone – appears to be bricked. I was still able to access bootloader mode last night so I tried flashing other ROMS – (two others to be precise) – but to no avail. Now (next day) I can’t get RSD Lite to recognize my phone – the battery was kind of low so maybe it died and having it plugged in via USB is not charging it?

Un-bricked!
Charlie,
Don't know if you were able to get your phone back yet, I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

basically i it flashes fine. i got a new battery for it. on rsd lite it says "pass" but the phone does not boot i cant get it into bootloader or recovery

I have my phone in similar situation, I was trying to update to Froyo/( KR 3.4.2-72) from stock german eclipse (2.51) and now i am with a white LED when i power on.
I flashed many roms 3.4.2-xxx......and stock 2.51 with RSD lite 4.9, it shows finished but doesnt restart itself, it stays with the white LED.
SWDL.txt shows
04/20/11 02:40:35 000012fc Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:40:35 000012fc Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
and sometimes
04/20/11 02:45:11 00000230 Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:45:11 00000230 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR
Is it because the bootloader is corrupt? or ??
Can someone provide with a defy booatloader? and is it sufficient to flash this loader by rsdlite?
Thanks a lot!! (btw i have enough battery from a friend)

The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App

and use the latest RSD Lite to flash!

Mcdomms said:
The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks a lot! I learnt the above as a lesson!... not on (nearly)stock rom... but after one week of brick like situation. Accumulated some guts.. will try nandroid backup od froyo kr...

Thanks for the help guys. But I took my defy back to cex. They sent it off for repair and apparently they could not fix it so now I got a milestone as a replacement. Well at least now I can enjoy gingerbread on cm7
Sent from my Milestone using XDA App

[Q] Defy not starting after flash SBF - Bricked?

Hi there, I'm having some trouble flashing my Defy. Here's what happened:
1) Bought my phone today. Installed a couple of apps (Foursquare, Twitter client, 1 or 2 others).
2) Rooted, then installed 2nd Init. Reboot twice, 2nd Init was working fine, I was able to get into ClockWorkMod Recovery with no trouble.
3) The main reason I wanted to flash a new ROM was to record videos at 720p, using Hancock's ROM 720p port. So, decided to get Barebones v1.5.
4) In the thread, it says: "If Your Coming From An Eclair Build Please Flash The Korean sbf, 3.4.2_74-Stock.KR_BLUR.sbf, Beforehand"
5) Downloaded and flashed the SBF using RSD Lite (already had Motorola's drivers and Android SDK installed, so no trouble here, too).
6) Flash the mentioned SBF with apparently no issues. But, when RSD reboots the phone, it simply shows nothing on the screen, nor does the screen light turns on. It looks like the phone is off, it simply does not boot.
7) When plugged to PC, RSD still recognizes the phone. Tried to flash the SBF again, with the same results (when RSD is flashing the SBF, the screen turns on with the "FW Update - In progress" message). RSD is still recognizing my phone, so I'm still able to flash SBFs.
So, what should I do? It looks like my phone is in bootloader (since RSD is recognizing the phone), but with screen/screen lights off. Should I try another SBF? Is my phone bricked? Thanks for your help!
P.S.: Some useful information: I'm not new to the ROM Flashing universe. Had been flashing my phones since I had a SonyEricsson K550i, at late 2008. Already flashed some ROMs to my HTC Magic, but it has none of these downgrade-locks or any stuff like these. So, I'm completely able to follow instructions on ROM/SBF/whatever flashing, and I'm 100% sure I followed all the instructions correctly.

I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App

mys_721tx said:
I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks for sharing, bro. Got the situation under control here, just flashed an american SBF and got things working. I think I just got a corrupt download or something like this.

on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "

vuhothang said:
on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "
Click to expand...
Click to collapse
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording

In case of stuck in startup
try
Pull battery,
put battery back in holding the VOL-Down until the android pops up...
press VOL-Up and VOL-Down at the same time.
Next screen is for wiping and updating.
Wipe Data/Cache

K3n H1mur4 said:
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording
Click to expand...
Click to collapse
hy..can you please post some screenshots on barebones..thx

I've tried several sbf now. But no one works. RSD lite shows "finished" and "pass", but the Defy stays dark. No reaction on pushing the power-button. only rds lite still recognizes it. any ideas?

The only sbf that works for my Defy is the following one for Defy+ http://forum.xda-developers.com/showthread.php?t=1385868

This means you have flashed a SBF that is not allowing a direct downgrade (flashing another SBF with wrong CG codes => Defy won't boot). Unfortunately at the moment there is no workaround to go back to Froyo or other GB versions that have CG31,CG35,CG39 code lower than 6 and CG47 lower than 3.
This happens wen users are not paying attention to warning messages.

Have you wipe DATA/cache before flash the SBF?
Use the latest driver and RSD.
BL=?

[Q] How to go back to official 2.1 optus for defy

Hey guys,
for a long time now ive been playing around with my phone and flashing different sbf's and roms and whatnot and now that the official update for the defy has come out on optus i would like to go back to the stock 2.1 so that i can update.
when i tried flashing the optus sbf, even after wiping everything the phone stays black and a the notification led turns white and my phone is only detected by RSDlite so then i tried the telstra one because originally my phone was from telstra and after i rebooted it still says im running android 2.2.2 and it looks exactly the same every time.
i realize i may have flashed a non downgradable sbf but isn't there a way to completely start from fresh, no os or anything?
-ashur

HELP!!! Flashed with many SBF files yet still stuck on M Logo

Hello,
I read most of the threads on this very topic and I can't seem to find the answer so please don't yell at me for starting a new one. Most of the people had their problems solved in those threads with one of SBF files but I can't seem to find any that can boot my defy.
I have tried to flash my defy with 8 different SBF files but still am stuck on M logo, which is sometimes white and sometimes Red with different SBF files. My original defy was froyo based and it had white M logo (hoping this info may help somehow).
I cannot get my defy to boot with any SBF that i tried. I am in Pakistan and I couldn't see any defy files for Pakistan. my bootloader is 09.10 and RSD recognize my phone as S Flash OMAP 3630.
Can anyone please tell me if there is a SBF file that can boot my defy or atleast allow me to access my recovery mode so I can restore my original froyo version? I tried many times but I can only access bootloader and not the recovery mode.
I am also doing all of the flashing with my SIM card inside the phone, is that correct way or am I making a mistake doing it this way?
Is there a universal basic SBF file that can flash every defy no matter which region it belongs? I would love if such a SBF exists.
I would really really appreciate any help,

I think the sea 15 sbf should work here is the link forum.xda-developers.com/showthread.php?t=1093352
Just follow simple instruction..
If you instal any ROM from gb kernel than it will be hard for you to get back to 2.2.2 if you hadn't flashed a proper fixed sbf i have bad English

Thanks, I will give this one a shot and let you know if it worked or not.
PS my Defy has a T-Mobile logo (US company) on it at the back, does all Defy models even sold in like India has those? and what does that mean for my Defy?

What sbf have you flashed so far....
For ur region sea 15 I'd recommended...
After flashing sbf I'd u get boot loop goto stock recovery and wipe the data...
Make sure u don't flash ginger bread sbf...
Sent from my MB525 using xda premium

Where did you got your defy? Is it having blur or is it the de blur version? In India I think all defy are with motorola logo at back with sea 15 sbf version

I purchased mine from a local company that sells all sort of cell phones. But, I am not sure where they purchase their phones. My Defy indeed had Motorola Blur and T-mobile logo at the back. Thats why i flashed my Defy with US and UK variants of SBF files listed here:
and-developers.com/sbf:defy
I also tried chinese and Nordic versions with no luck at boot. Even if I somehow can access my recovery mode I can atleast go back to my original defy by doing factory reset and resorting it to the way it came in.

Ok I tried the sea 15 sbf along with the Chinese Eclair sbf that people put after putting in gingerbread for going back. Yet i am still stuck in logo M. I cannot get into boot recovery mode at all, I tried everything but I can only access the BootLoader and not Boot Recovery.
Please tell me How can i access boot recovery so I can wipe everything and do factory reset and get my defy back to life.

I had the same problem and it was really funny. I had Defy Retail CEE with Android 2.1 and next Official Froyo 2.2 CEE too. I was selling it few weeks ago and needed to wipe phone, I wiped data and cache and after this phone stuck on Moto logo. I was trying every sbf. for Europe starting from early versions of Eclair ending on official Froyo and nothing. After this I just removed memory card and wipe data/cache and phone turns on on stock Froyo. Memory card wasn't damaged cause i was using it with this phone and was ok but it just can't boot first time with this card inside. Next boot was ok with card inside.

Xperia arc updated to 2.3.3. And then updated to 2.3.4 from mobile. now won't turn...

I tell you I unlock it first, then I had problems with some widgets and I learned some new updates.
Then, I made a backup with Sony_Ericsson_Backup_and_restore.
After searching, I root my phone with "GINGERBREAK" downloaded from the internet (GingerBreak-v1.20) and finally settled "Titanium Backup" to remove some applications from my operator, then install the CLOCKWORDMOD (do not know what for) and and finally I started to flash ...
After root, flashing with FlashTool_0.2.9.1.
I suggested steps for flashing and inserted this update: "LT15i_4.0.A.2.368_Generic Global", with "wiped ...", which is to delete everything and set it to zero ..
Normal work for me ... I sent version 2.3.2 to 2.3.3 (thinking I would send to 2.3.4). It was great ... Then I appeared a notice of samsung (on phone), to install version 2.3.4 (4.0.1.A.0.283 I think it was that number) and when it started to install warned me he was going to shut down, spent 6 or 7 minutes and not lit. I tried to turn it on and vibrated, then vibrate him again and try to turn rang again, but soon ...
Then I could not turn ...
Once this happened I was like crazy trying to fix the COMPANIOM, but nothing ...
I flash again, this time with this "LT15i_4.0.2.A.0.42_ (1247-1041). Ftf" but did not recognize the flashtool as the first time coming out of the mobile code when you open the program loads and displays the model number of the phone, it did not appear.
Finally, press flash and began. (To this already, before, try reinstalling the Global LT15i_4.0.A.2.368_Generic where my computer does not recognize, nor giving flash, just not recognized out in red letters)
When flashing with the latest LT15i_4.0.2.A.0.42_ (1247-1041). Ftf, the normal flashing until the end. But my phone just did not work. The light that was on the side of my phone was green ...
I sent a technician and he said he could not ....=/
I hope you can help and serve as a case to be resolved.
Thank you very much, good luck!