[Q] My Defy really is Dead! - Defy General

Ok my phone is DEAD! Yes I have have read alot of posts and used my mate "Google" but they are all saying or pointing to the threads saying flash with the .sdf files with RSD which I have done Infact i've tried most .sdf images. I work in ICT so I know to do research first before posting but I'm not getting anywhere. I just hope i'm being a numpty and missed something.
I have an unbranded UK one original version 2.21 and I had successfully flashed with the available roms on here and others by following the steps, but last night I flashed it with PAYS rom and it was fine but then it all went pear shaped when I tried to flash it back to the original 2.21 rom via RSD Lite but it's just a black screen and when plugged in I get a charge light. The Battery is fully charged.
I can not enter Bootloader and when I enter system recovery it does not respond when pressing the bottom right hand corner.
RSD does see the phone connected and it runs through the process of flashing it but then it goes to re-boot and nothing. RSD says it's finished, it does not go through the process of re-booting the phone.
In RSD on the phone properties this is all I get:-
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e600209036f60010000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: a9e56c008df05759e72a50cf0e4ce907eea6c0de
Please, please somebody help me!

Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App

chaihg said:
Simple way to start off is to start with original UK 2.51 sbf. Forget 2.2 now and start from beginning. I bricked mine trying Pays too.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Hi,
I have tried flashing the 2.51.sbf even tho it has the problems with downgrading. It does the same as the the other 5 or 6 i've tried.
Thanks for your suggestion tho.

I'm no expert, but is this where the touch all four corners going clockwise starting is upper left comes in?
Thought I read something about doing that when touching the single corner didn't work to get into recovery.
I could have misremembered (don't even know if it was in this forum), but it couldn't be that hard to try and it doesn't sound like you have much to lose.
maybe search four corners or something to figure out more.

Maybe time for factory repair

ABC_Universal said:
Maybe time for factory repair
Click to expand...
Click to collapse
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!

In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.

it_ferret said:
I think it may be time to call Motorola. Thanks for the tips guys.
Just tried the battery hack to charge it but nothing, even uninstalled everyting and downloading fresh .sbf files from work and still DEAD!
RIP Moto Defy, it was only one week old!
On a life experience tho, my first even bricked device......woooohoooooooo!
I've had quite a few phones that I have customized from here, top effot guys. There are many greats minds on here.
Think as i've just lost it, it could be time to retire and go (dare I say it!) mainstream, run of the mill Nokia.....GULP!
Click to expand...
Click to collapse
Did you send it away?. You sounded like a bright guy we could have solved this together though . Ultimate thing you could have done was to flash one of the leaked original UK froyo sbf. If you still have not sent it then do this. BTW what is the bootloader version when you put it on vol up+ power ?

Have the same problem
The phone is briked. Only RSD is working but wathever sbf I flash, at the end i get the same black screen. I can not do anything. Please could someone help us?
If someone send their phone to service, please share the result.
The only sbf file that start the phone is
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF.sbf
but is working hard, the market is not working, everything i want to download is say that is downloading and nothing hapends.
Could someone tell me how to go back to original software?
The recovery mode is not working, when the android face is showing, i tap all corners and all display area but nothing hapend.

For recovery mode, you should click both vol up and vol down simultaneously. They changed the recovery button function with the new bootloader.

it_ferret said:
Ok my phone is DEAD! .....
Please, please somebody help me!
Click to expand...
Click to collapse
I had the same problem, but with luck i had read this thread :
http://forum.xda-developers.com/showthread.php?t=940647&highlight=market
and i succeded to restore my "brick" into one working phone.
Try it.
Many thanks to : adlx.xda

Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
Umm... I just bricked mine (HK version 2.51.0) as well.
I used ClockWorkMod Recovery for Defy to install 3.4.2 131-003 Orange Deblur. When the recovery finished, I found a tiny yellow line "E: can't open /cache/recovery/command" on the bottom of screen. Not sure if it was there before the recovery. When rebooted the phone showed the M logo for a minute, turned black for a second, and showed the M back again in loop.
Then I installed RSDlite 4.8 to flash the sbf directly. RSDlite finished and showed a "Pass". The phone was turned off automatically but couldn't be turned on again. The battery was fully charged before I started the update so it's not likely the battery charge problem.

Weudel said:
In the future it would be better to post these issues in the thread of the ROM you are having issues with. More people who may have had similar issues may be able to help you and it helps the dev know what issues you're having.
Click to expand...
Click to collapse
I did post in the thread.

Heys guys thanks for all the comments, but last night it came alive.
I used 3 different computers and in the end the last pc I used was a WIN 7 x64 machine and it managed to complete the .sbf install which was a 34.4 version then i applied my previously nand backup to 34.4.4 US T-Mobile version which is Jboogie3 rom.
Keep up the good work guys and gals. This is an excellent community to be in.

ABC_Universal said:
Edit: http://forum.xda-developers.com/showpost.php?p=11226369&postcount=5 works for me
I tried this install but that aswell failed.
Click to expand...
Click to collapse

im a newbie at this and did pays flash but had probs couldnt dial out ect ect so went to recovery but could not get bottom left hand screen work so after half day of trying i clicked both bottom -vol and top+ vol and restart button on top and it worked!!! but thought id give the rom one last go so did factory reboot flashed cash ect restarted signed into blur and now works great pleased i stuck with it...cheers pays

Related

Motorola Defy Bricked? Can you help?

Hi,
this is my first message here and I hope it is in the right place.
Only 2 days after getting my defy I already managed to brick it.
Basically, I wanted to add hebrew fonts, was playing arround with a file explorer trying to copy the fonts from the microSD to the /system/fonts/ folder, then as the files were not copied I deleted one of them and tried again. Continued playing arround and then did a restart. Only Motorola logo is showing.
I tried the down arrow for starting in "Android system recovery" and tried both wipe data/factory reset and wipe cache partition. I also tried to apply sdcard:update.zip with only the fonts in it. no luck.
I am reading and reading and not finding anything... Can someone please help me?
i think bricked is when it doesnt start at all, so its not that bad
Someone help this guy
psbh, how do you think the defy feels in hand, i like metalic phones , im not sure with this one, its light and plastic
do you value the build quality extremely , like me?
if so does it feel cheap?
thanks for your reply mariu$!
i have to admit that i already solved it by myself ~embarassed~. i should learn to try everything before i am crying for help like a lil girl.
if anyone would get to see this and had the same problem, how i solved it was by installing RSD Lite and flashing the phone with a new .sbf file. i did feel like i was close to die from sadness...
to the defy: the phone indeed feels cheap and i really doubt its outdoor "abilites". it is light and the big screen and fast processor makes it worth the 300€. i have it since 2 days and already dropped it a couple of time and it stayed one piece
i really dont want it o be cheap
do you have the white version? i think that it looks cheaper because it's as it has a rubber band arround it
i saw you mentioned the price in euros, so you bought it in europe, hows the call quality your hearing?
thanks for your answers
I agree that the white version looks cheaper, thats why I got the back one. At least from the front it looks good
I havent had the chance to call with it yet I rarely ever use mobile phones for calling... but the rest is great!
ill probably buy it too
i think after i dive it in the water a few times, it wont feel cheap, after all not many phones can do that, and it must be build seriously to be able to do that
My alternative was the XT720, but i hate the side part and the blue back
The Build quality however is exceptional
in my opinion it doesn't FEEL cheap. I could understand if someone would say it looks cheap from the back though, but i really like the design.
psbh said:
if anyone would get to see this and had the same problem, how i solved it was by installing RSD Lite and flashing the phone with a new .sbf file. i did feel like i was close to die from sadness...
Click to expand...
Click to collapse
help me please ... i bricked my defy also , but where to find the right *.sbf file ?
* push * anyone able to help me reactivating my bricked phone
amsoft said:
* push * anyone able to help me reactivating my bricked phone
Click to expand...
Click to collapse
I got mine back to life after screwing around too much. I'm not allowed to post links yet, so go to the forums at modaco dot com, search for Defy threads started by dkspook, scroll down to the long post on page one. I even posted all the tools you'll need
Please post your results!
@Sorensiim : It works, thanks bro ! i was already near throwing this phone out f the window, thanks again for your support
You can't brick a phone by flashing roms (assuming the rom has no radio image) or recoveries, but can when flashing a new radio image and i think when flashing a new SPL bootloader
Your phone is fine if you can get into any one of the following:
ROM
recovery
Bootloader (fastboot ect)
its when you can not get into any of these, you have a true brick.
Please correct me if i am wrong
Can this help:
http://forum.xda-developers.com/showthread.php?t=853674
Real Brick..
Guys I really need some help here.
I've really bricked my phone! I cant flash any ROMs, even small BOOT ONLY ones.
All I get is "error flashing subscriber unit" error...
I've tried RDS Lite 4.8 and 4.8, with Drivers, every time clean uninstall and install.
RDS can see the phone no problem, I've tried changing setting in RDS, no luck...
This is the log from RDS:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE0030009 Address: 0xB101F000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=35
All this happened suddenly after flashing to Chinese 2.2 with Higgsy Mod coming from stock T-mobile UK.
I've searched everywhere, but no one know what's going on.
Any Ideas Please...
Bricked defy for sure
My defy isnt starting at all, was flashing a sbf file when my windows crashed and now my phone is neither entering recovery nor bootloader. I think its bricked but any suggestions would be appreciated( urgently needed).
Everything needed to flash a defy, don't kill it and know what you are doing is in a Sticky in the forum. Very first post.
Edit: That's what happens when you dont see the post date hehe.
To the last poster, if you cant really enter Bootloader or Recovery, I'm afraid you really have a Brick
Rish13 said:
My defy isnt starting at all, was flashing a sbf file when my windows crashed and now my phone is neither entering recovery nor bootloader. I think its bricked but any suggestions would be appreciated( urgently needed).
Click to expand...
Click to collapse
First make sure your battery has a full charge. You can look up the McGyver usb charging method. Your battery might not have a charge anyone. With this method you can flash another sbf. If this doesn't work then yes, you have a brick.
LG G2x EB 2.3.3 v. 1.07
Motorola Defy MIUI 108190
Rish13 said:
My defy isnt starting at all, was flashing a sbf file when my windows crashed and now my phone is neither entering recovery nor bootloader. I think its bricked but any suggestions would be appreciated( urgently needed).
Click to expand...
Click to collapse
This happened to me, the phone wouldn't turn on but when plugged in, RSD lite still recognized the phone. If this is the case flash away. Always make sure your battery has enough juice in it. Good luck!
LG G2x EB 2.3.3 v. 1.07
Motorola Defy MIUI 108190
Thanks for your replies guys, btw can you please elaborate on McGyver usb charging method, and my phone is not at all recognised by rsd lite and initially when i was about to flash ie when my phone was is a working condition i had some issues with rsd lite v4.9 too, it would flash only one specific sbf file and none other would start(start bar wouldnt get highlighted but for that one specific fixed sbf file), the only thing that i can see on my phone is when i connect it to usb a white led glows, and finally god forbid if my phone is bricked what do i do? take it back to the shop coz its still within warranty(hardly a month over ) is it ruined by all the firmware stuff that i did? This is one of the best phones ive ever and i dont wwant to lose it. Please help me out! Eagerly waiting for your suggestions...
McGyver USB method
http://forum.xda-developers.com/showthread.php?t=892026
I also got the white LED, have you tried pushing volume down while the phone is connected to your computer with RSD lite running, when I did this, RSD recognized my phone even though my phone didn't show the bootloader. As far ar sbf files I not all worked with my phone. I tried a good deal of sbf's. Try until you find one that boots up.
http://and-developers.com/sbf:defy
I think the one that worked for me was the UK Tmobile Build # JRDNEM_U3_2.51.1.
I used baseband switcher after flashing both CM7 and MIUI (current) to get 3g working.
http://forum.xda-developers.com/showthread.php?t=1052745
Good Luck man

[Q] Defy is dead on flashing

Hi,
I was flashing the UK Sbf on a unbricked phone using RSD Lite 4.9. During the flashing process, suddenly phone turned off and disconnected with RSD Lite displayed a message "Failed, Device disconnected error".
I actually had 40% battery b4 starting the process. is it the low-battery problem?? Now, I am not able to do anything with the phone. When I have plugged in for charging, it says nothing. Is it dead?? But, when I have connected to the USB, a white small light comes on the top.
How to get my phone back? My phone is from Honk kong and i have rooted it as well.
Would u please guide me if we can do something??
Many thanks in advance,
Regards,
Naga
Charge your battery in another phone or in an universal charger and try to flash once again. Or you can repeat flashing procedure on another PC.
nagnrik said:
Hi,
I was flashing the UK Sbf on a unbricked phone using RSD Lite 4.9. During the flashing process, suddenly phone turned off and disconnected with RSD Lite displayed a message "Failed, Device disconnected error".
I actually had 40% battery b4 starting the process. is it the low-battery problem?? Now, I am not able to do anything with the phone. When I have plugged in for charging, it says nothing. Is it dead?? But, when I have connected to the USB, a white small light comes on the top.
How to get my phone back? My phone is from Honk kong and i have rooted it as well.
Would u please guide me if we can do something??
Many thanks in advance,
Regards,
Naga
Click to expand...
Click to collapse
Don't worry.
If the white led brights on the phone, it is possibly charging.
If not, read the following thread, there's the solution:
http://forum.xda-developers.com/showthread.php?t=926012
BE CAREFUL WITH IT!
Well, thanks for the quick repsponse guys... I try this... Hope, it works...
I have tried it... no luck.... But, I am a bit sure I have connected those wires properly n mounted the battery..... I got this mobile from Honk-kong.. I was actually flashing a UK Firmware (SBF)... Does it matter?? I did not wipe or any resets prior to flashing.. I have successfully rooted the mobile after Hard trails... thought of flashing it to froyo... But, mistakenly did this... )..... It went well till 73% and suddenly disconnected error and phone turned off with a white light on the top..
Any other way other than sending it to Motorola support... And I am in Dubai now.. this mobile is still not available here... so no local support from Motorola end. I have to pack it to either UK or HK...
Any trails???
Many thanks in advance.....
What .sbf are you flashing? The 2.34 or 2.5.1?
nagnrik said:
I have tried it... no luck.... But, I am a bit sure I have connected those wires properly n mounted the battery..... I got this mobile from Honk-kong.. I was actually flashing a UK Firmware (SBF)... Does it matter?? I did not wipe or any resets prior to flashing.. I have successfully rooted the mobile after Hard trails... thought of flashing it to froyo... But, mistakenly did this... )..... It went well till 73% and suddenly disconnected error and phone turned off with a white light on the top..
Any other way other than sending it to Motorola support... And I am in Dubai now.. this mobile is still not available here... so no local support from Motorola end. I have to pack it to either UK or HK...
Any trails???
Many thanks in advance.....
Click to expand...
Click to collapse
Can you start it in flash mode or recovery mode?
(vol up + power or vol down + power)
Hi, I am not sure of this as I have downloaded too many files for rooting, froyo upgrade and other stuffs.. But the file name is "UK_rom.sbf" and size 370MB+. are there any consequences??
avers said:
Can you start it in flash mode or recovery mode?
(vol up + power or vol down + power)
Click to expand...
Click to collapse
Yeah, I have charged it for sometime and trying to POWER+VOLUME-UP for boot loader only... It looks like dead, no repsonse from it... when I have put it for charging, it did not show any indication that it is being chraged.... anything went wrong???
nagnrik said:
Hi, I am not sure of this as I have downloaded too many files for rooting, froyo upgrade and other stuffs.. But the file name is "UK_rom.sbf" and size 370MB+. are there any consequences??
Click to expand...
Click to collapse
Ok, go here http://and-developers.com/sbf:defy and download an sbf, I use 2.5.1, however once you flash it you cannot downgrade it,,, There is owever a lot of develpment more recently for it, im running a smooth froyo on it now.
Anways, pick one, extract that file to your RSD folder.
Open your RSD lite
Pull the battery from your phone, wait a few seconds, put it in, and boot into bootloader (vol up and power).
Plug the phone in, as long as the white light comes on you should be good...
select your new sbf file and hit start on RSD, you should work..
Now depending on what you had prior, your only option may be to flash 2.5 which is what I had to do.. Again, Id rather have a phone that turns on then complain about not being able to downgrade..
Let me know
good luck from my side
hint: never used a file called "UK_rom.sbf" - little unspecific ;===)
-nevermind- good luck once again, hope you bring it back to work!
Well, mobile it self is not turning on... It is a strange issue.. And fortunately, It has been launched here a 3 days ago in UAE.. I went to a store to check if the issue with the battery.. I have replaced and tested it out.. No luck.. I did not c the % of the charging. May be Bootloader requires more charging than normal powering... Anyways, I am decided to submit it to Motorola here, they must help us out...
Thanks everyone here for the wonderful support.... love XDA.... keep u posted as soon as it is fixed.... Many thanks again....
I deserve a beer for this!!!
Did the same goof up....got greedy for froyo and couldn't resist f&(*ing my defy........was cribbing for 8 hours while figuring out the solution.... escaped office for this.....but finally finally .......i saved it.......man.....if blood is the answer for blooood....then it has to be 2.51 for 2.51....
please click the link below for the only feasible 2.51 sbf....flash your defy in a standard manner and kabbooooom........defy reincarnated...
:
hope it works for all the good people in need....it worked for me (Atleast my defy turned on still observing how it works)..
Defy 2.51 sbf
Sorry for being late to the party, but how did this turn out eventually?

[Q] Help needed :) phone dead, mcgyver doesnt work, no rsd lite recog.

hey guys,
the original thread is located here: http://forum.xda-developers.com/showthread.php?t=940647
i did everything according to the description...
directly after flashing chineese stock rom^^ .... came back to the pc (wasnt there during flashing, but nothing could have happened, only rsdlite running, phone wasnt recognized, phone was off, white led on)
(battery has been fully charged, so battery is okay)
i tried everything, volume up + power, didnt work, rsd lite cant recognize. nothing here...
maybe someone can give me advices? no chance here so far to get it recognized in rsd lite.
thanks - appreciate any help,
but i got the really bad feeling that i've bricked my phone - OMFG guys.
edit: omfg, now there is a warning. it wasnt there when i flashed it, on the links stands, u can flash some leak, BUT - no rsdlite, no fllashing^^ ? right?
edit2: read some more posts, will try mcgyver hack 2morrow, invited to a party right now^^ so without a phone meeting some people always a litte bit more complicated :====P ***so thumbs Up *** for my little person for tomorrow. cant explain why the battery should be completely empty? but hope, that white led just means that. - will report 2morrow -
edit3-solution?
my defy is already on the way to service, BUT
someone told me: ! --> HOLD THE POWER UP KEY - BEFORE u PUT THE BATTERY IN ...
this worked for him.. maybe this could help anyone else! good luck to everyone!!
this work for me
http://forum.xda-developers.com/showthread.php?t=892026
just flashed the chinese 2.2 with RSD lite, all went well, RSD gave a "pass" result to the flash And now the phone will not turn on, no lights or anything. Charge light doesn't even come on when plugged in, if i press power when it is connected to charger, the led flashed white once and nothing else. I had 3/4 full charge when I began, don't see how the battery could have drained out, but I will try charging externally
Also I was coming from T-mobile Eclair 2.1
ok, so my first flash I used a flie I downloaded labled 2.2CN_SBF.sbf
So I reconnected the phone to RSDlite, and it showed the device was connected, I downloaded the Chinese.SBF from Higgsy's page and still nothing but a dead phone, its definetaly not the battery if its connecting to RSDlite and letting my flash, and reflash. Maybe I will try going back to stock 2.1 sbf
make sure your set to first-Come-first serve Deviceid mode in rsd lite config
I've tried flashing the orignal offical UK SBF, and a Lite Chinese 2.2, nothing screen is black, can not get into recovery, phone stays in bootloader but has black screen although says SW upate when flashing
crazyVII said:
hey guys,
the original thread is located here: http://forum.xda-developers.com/showthread.php?t=940647
i did everything according to the description...
directly after flashing chineese stock rom^^ .... came back to the pc (wasnt there during flashing, but nothing could have happened, only rsdlite running, phone wasnt recognized, phone was off, white led on)
(battery has been fully charged, so battery is okay)
i tried everything, volume up + power, didnt work, rsd lite cant recognize. nothing here...
maybe someone can give me advices? no chance here so far to get it recognized in rsd lite.
thanks - appreciate any help,
but i got the really bad feeling that i've bricked my phone - OMFG guys.
edit: omfg, now there is a warning. it wasnt there when i flashed it, on the links stands, u can flash some leak, BUT - no rsdlite, no fllashing^^ ? right?
edit2: read some more posts, will try mcgyver hack 2morrow, invited to a party right now^^ so without a phone meeting some people always a litte bit more complicated :====P ***so thumbs Up *** for my little person for tomorrow. cant explain why the battery should be completely empty? but hope, that white led just means that. - will report 2morrow -
Click to expand...
Click to collapse
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
nitski said:
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
Click to expand...
Click to collapse
Was forced to flash the leaked froyo tmobile signed SBF. Forgot that this Defy wasn't the orignal, my wife had it replaced due to Earpiece failure, so the replacement must have had the OTA already, cause i never installed it. Oh well its her damn phone anyways LOL
Just curious how would you check next time to see if its 2.51
So to sum up CrazyVII, You have to flash the Froyo Leaked SBF with the signed keys, otherwise you will never finish the bootloader flash.
Just connected to RSD and make sure its set to First cum first serve, and hit the power button on the phone, screen won't light, and my led didn't either, but it should safe connected in slot one of devices.
Start Flash, and wait to see the "M" , RSD will let you know when to restart the phone.
Hopefully they figure out how to make this downgradeable, I perseonally Have a G2, but I really enjoyed Rooting, and deblurring my wifes phone, its a nice device
nitski said:
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
Click to expand...
Click to collapse
seriouus answer? dont want to wait until a new one arrives..
Dalamak said:
So to sum up CrazyVII, You have to flash the Froyo Leaked SBF with the signed keys, otherwise you will never finish the bootloader flash.
Just connected to RSD and make sure its set to First cum first serve, and hit the power button on the phone, screen won't light, and my led didn't either, but it should safe connected in slot one of devices.
Start Flash, and wait to see the "M" , RSD will let you know when to restart the phone.
Hopefully they figure out how to make this downgradeable, I perseonally Have a G2, but I really enjoyed Rooting, and deblurring my wifes phone, its a nice device
Click to expand...
Click to collapse
thanks for summing up,
u mean the chineese froyo release is something like the 3.4.?.? version? im going to search for it right now
maybe anyone can supply a link?
the problem is, i tried nearly evey combination, the phone doesnt recognized by rsd lite.best proposal would be - battery out - in - vol up + power - wait .... rsd lite doesnt do anything.
so very hard to flash.
do i need to apply the mcgyver trick, or is it useless....?
edit: why can't the phone load while off? i just understand the logic behind this behaviour...
best reagrsds thx,
cV
phone really dead.
guys, tried mcgyver trick....
white light goes on on usb connect directly... dont know why, but nothing worked. first come first served mode enabled in rsd lite.
rsdlite running the whole time. nothing connects, nothing realized.
direct boot (only power button), power + volup button, everything. no result.
the strange thing, in the meantime i saw someone posting, he flashed the whole thing(as in the description, 1st post) on 2.51 and on his phone everything worked fine.
no idea. but i think mine is really gone now. i think ill send it to my reseller tomorrow. im not quite sure if i can stay with such a situation (not loading in boot loader mode? WTF? no real recovery image? F*CK? bad hacks? no useful backup situation.. why do i need a recovery, when i cant access it when i screwed up? -> useless to me.
im really thinking of switching back to htc, although the DHD is too big, i think ill gonna take it
guys, any tipps? suggestions? id really appreaciate it. :=)
thanks for all the responses so far.
current situation
- mcgyver trick tried for 45 mins,
- rsd lite in first come first served mode
- white led goes on on usb connect immediately
- screen is black the whole time
- no results - no recognization...
- flashed chineese 2.2 on 2.51 firmware
Did the same goof up....got greedy for froyo and couldn't resist f&(*ing my defy........was cribbing for 8 hours while figuring out the solution.... escaped office for this.....but finally finally .......i saved it.......man.....if blood is the answer for blooood....then it has to be 2.51 for 2.51....
please click the link below for the only feasible 2.51 sbf....flash your defy in a standard manner and kabbooooom........defy reincarnated...
:
hope it works for all the good people in need....it worked for me (Atleast my defy turned on still observing how it works)..
Defy 2.51 sbf
Theres more....though i sacrificed one of my data cable for mcgyver jugulary...but got a wonderful outcome of my 12 hours wait..........my earlier (india) rom was not full blur...never realized it...facebuk never synced......but this uk rom is FULL BLUR..and its awesome......alll my accounts are intact......everthing works just fine....in face some of the the apps which never used to work earlier work flawlessly now........
ACCIDENTS ARE NOT ALWAYS BAD
All those greedy people wanting to flash froyo from 2.51 and wanting to keep their downgradability, you will need to search for tutorial from Bihariel where he put up froyo rom only for 2.51 base.
All the best.

[Q]

I might ruined my defy+
When I bought it, it was in German, i changed it to dutch and had android 2.3.6
Flashed it with the all-in-one Defy beginners guide
Had a working android version afterwards, only calling/sms/2g and 3g didn't work. Didn't try to fix it because i wanted to flash the latest cm7.2.
Don't know what i did after that (afterwards we went to carnaval, so i drank to much). I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1040020f1fab3a0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 9aff8fe986ef65565a0a1e805942bbeaa8460f87
BP Public ID: 0000000000000000000000000000000000000000
Tried different roms, didn't work. Tried the following
"Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backupwent wrong here, multiupload is gone so couldnt continue
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot"
Anyone got a answer for this? I am searching this forum for over 6 hours in the last days.
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up?
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!
niksy+ said:
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up? Yes nothing shows, looks like the batt is empty but that isn't the case
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
No nothing
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!Didn't came to that
Click to expand...
Click to collapse
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
taarmen said:
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
Click to expand...
Click to collapse
Not really, buddy :-/
You should have answered my questions, that way I could have written you a step-by-step guide
What you should do:
0. Phone's off
1. Enter stock recovery
2. Wipe data and wipe cache
3. Turn off phone
4. Enter bootloader
5. Flash full stock 2.3.4 sbf - http://www.mirrorcreator.com/files/1HLS00W4/
6. Your phone should boot up normally after the process is done
If you can not enter stock recovery, then just enter bootloader and flash the sbf. The thing is, those fixed sbf's don't have all the codegroups, so some stuff from CM7.2 has probably remained in your system. Full sbf should do a much better job. But, it would be great if you can enter stock recovery. That way the flashing must be successful.
Note, I haven't tried that 2.3.4 sbf! But it's the only one I could find. I need it too and I will test it tomorrow morning, so if you want, you can wait for me to test it first. (I need it cause my defy+ is on Froyo now, and Froyo and defy+ don't really like each other ) I have tested one 2.3.5 sbf, I can point it to it if you wish so. (It doesn't matter which android version it is, as they all have version 6 signed codegroups, so you can switch between them without worrying! Only some latest 2.3.6 ROM's are signed as version 7, but it's highly unlikely that you have flashed your phone with one such)
I Agree with niksy+, can't help, I have a Green Lens Defy, so all i have to say is good luck, and a step-by-step would have been nice
Thank you for the effort, my defy+ is braindead. When i connect it to my pc the white top led goes on. And that is it, nothing on RSD, wont boot, wont go in the bootloader
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Click to expand...
Click to collapse
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
i have the popcorn out for this one - fun thread! will the defy be rescued??? tune in next time, same bat board, same bat sub board!
taarmen said:
I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
Click to expand...
Click to collapse
If the UK 2.3.6 ROM you installed was this one then you will not be able to downgrade to any other 2.3.6 ROM (except I think this one), let alone 2.3.5, 2.3.4 or Froyo (it does say that in the thread you linked).
You should still be able to flash either of those 2.3.6 ROMs with RSD Lite. But no other ROM - until some more with CG 7 or above become available - and it's currently not rootable either. So no chance of CM7 or other such like goodies. At least you should be able to get a working phone that you can sell on eBay if you desperately don't want to be stuck with the T-Mobile 2.3.6 ROM.
Morals of the story:
1) Read before you flash
2) Keep a written record of what you did (I know, boring)
Good luck, let us know how you get on.
niksy+ said:
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
Click to expand...
Click to collapse
Wel I hope that iolinux333 has enough popcorn because non of the mentioned forced bootloader steps works
When i put my + on the usb nothing happens for a few minutes after that a withe led will shine. Thats all.
Thank you all!
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Fotogravin said:
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Click to expand...
Click to collapse
Been away for a few days. Back and ready to repair, I appreciate all your help.
no sim and sd-card
win7 64-bit
Battery is Full
RSD Lite version 5.6
motorola 5.4.0 usb drivers 64-bit
Tried all combinations at least 10 times. First I disconnect usb -> take out bat -> make combination and count to ten -> put in bat -> holds for minimum of 10seconds -> click on "show device" on RSD -> Nothing show
Nothing ever shows.
You really should give us more... What happens when you try to power it on? I think you only get black so, does power+vol(+) give you something or do you get a white led when you plug it in the pc?
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button. (like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
labsin said:
You really should give us more... What happens when you try to power it on?
Compleet black nothing happens
I think you only get black so, does power+vol(+) give you something
Still nothing
or do you get a white led when you plug it in the pc?
Yes I got that
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button.
Still nothing, not even the white led
(like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
Haven't been able to trie different pc's. Tried differt usb ports, even those of my mouse and keyboard so I know they fully function, only white led
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
nothing to show
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
Think i got to trie it,what can hapen if they found out i lied?
Click to expand...
Click to collapse
Thank you for helping me, I just tried RSD Lite 5.7 and also nothing.
Sorry a bit late. You didn't lie
I should be recognizable. Especially with a full battery. If not, you might have had a bad install and they might have to replace the botherboard.
If you don't mind waiting a couple of days longer, bring it to the place you bought it. Then the delivery costs are free. But could take 1-2 weeks longer.
IF they do conclude it is your fault then you have to pay an amount of money to deliver it back or you can pay for repairing it (for motherboard could be 80-100 or more, actually don't know). Again when you went trough shop this takes a week or so. (motorola => shop => 3 days nothing => you => 3 days nothing => motorola).
They are not that picky at motorola except for water damage maybe (check for a red sticker below the battery. If it is still white => no prob)
Thank you all. I've sent my phone to the store where i bought it, on friday and the next friday i got it back. With a fresh stock rom.

[HELP] Bricked, almost dead Defy+

i bought this Defy+ just a couple of days ago and i was trying to get CM7. I struggled to root it but i achieved it. I wiped and did all the procedure before installing it, but i didn't had enough space on my SD, so i rebooted and booted like a brand new defy, going through the Blur config and everything... So i went to Recovery again, but at this time i forgot to do the wiping - which, i guess, led to a brick.
So i managed to get a .sbf to flash it.. What i didn't realized is that the .sbf was a custom, so i guess this ****ed up my phone even more. And so i went on trying to rescue my phone but this time i couldn't complete the flashing process, i wasn't able to perform a downgrade - i guess. After this, i got a non-rootable .sbf and began the flashing. The process got stuck on some message at 0%, then i disconnected the phone.
When i was able to download a stock firmware, from the .sbf thread, the phone wouldn't reboot when RSD asked, it didn't turn on again. So i tried to re-flash it, same .sbf and now i'm stuck with this situation: the pc is not recognizing my phone, i have a black screen - not even the Bootloader error screen is appearing and i'm here, begging, for someone to help me. is it dead? can i get it back?
HELP, PLZ
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Auris 1.6 vvt-i said:
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Click to expand...
Click to collapse
it doesn't turn on, but i guess it does have battery, i can see the led on when i connect it to the pc
Led is always on when connected to the PC - it means nothing. If it doesn't turn on, then your battery's dead. Find someone who has the same phone and can charge it for you.
I think there is no problem, but you flash older firmware, which is probably due to the 7 bootloader does not go up.
try to be flash with one of these (2.3.6 GB)
http://forum.xda-developers.com/showthread.php?t=966537
begins with the 139-ended, if it is not going to work with the 188-ended
Sorry for bad English
"As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong."
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
caiowatanabe said:
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
Click to expand...
Click to collapse
If it gets past the red m and just keeps playing the android animation then simply pull battery hold volume - put battery in and keep volume - held when you get the android and the triangle press volume + and - and wipe all, should boot, unfortunately you've just flashed the un root able sbf and are stuck on moto standard
teamwork makes the dream work
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
caiowatanabe said:
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
Click to expand...
Click to collapse
Feel free to keep an eye on the dev section for the bl7 rooting thread you may get lucky
teamwork makes the dream work

Categories

Resources