help! Defy wont boot, white light at top, rsdlite doesnt recognise - Defy Q&A, Help & Troubleshooting

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
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

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

Related

Exceptionally Soft-bricked Atrix: Please Help

Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
xyrovice said:
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
Click to expand...
Click to collapse
If you get the starting RSD mode you might have a chance. Put your phone back into that mode and try flash back to stock SBF using rsd lite. Follow this guide: http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf
What version of software were you running before the brick? 1.26, 1.57 or 1.83? You will need RSD Lite - Download As well as the sbf for your version of software. Post back your version and I can give more guidance.
You may not need to flash all the way back to 1.26, I soft bricked today - as in can't get past the initial Moto screen with a flashing red light, and flashed 1.83 sbf.
I've actually tried to flash some of the SBFs- well, all of them, now that I think of it.
It always ends up in an error, though, and stops.
If you give me a sec, I'll try and recreate it. Off the top of my head, I remember it saying something about "Bypassing BP" or something like that.
Thanks for the fast responses. Lemme try and RSD flash here right quick.
PS (EDIT): I was on 1.5.7 running GladiAtrix 4.2.3 (if that makes any difference). I just started flashing 1.2.6 via RSD. I'll let it sit and see where it sinks.
Thanks again guys.
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
If you were on 1.57 I would try flashing the 1.57 SBF - this will retain a lot of your info, whereas the 1.26 will wipe your phone clean and take more work.
1.57 SBF Thread
You will need to root with gingerbreak to regain root if you flash the 1.57 SBF, Gingerbreak Thread. Make sure to copy the contents of mnt/sdcard and mnt/sdcard-ext to your computer so you can replace them after gingerbreak cleans them out.
xyrovice said:
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
Click to expand...
Click to collapse
Just putting that up there.
Also, I was in the process of trying to wipe my phone for a clean 1.8.3 flash, so a 1.57 flash to retain info isn't a big deal.
I went straight to 1.2.6 in the hopes that the retail version would be more likely to go through (for whatever reason).
Thanks for bearing with me.
Take out your SIM card and SD card if you have one, restart your computer and don't start any other programs besides RSD Lite to allow it the most resources (I've had it fail a few times without enough resources). Start RSD Lite and load up the SBF, turn on the phone and boot to RSD mode with the volume up button, once in RSD mode plug the phone in and start the flash. I don't know if any of this will work for sure but these are all steps to help the process.
try multiple cables, computers, OS's, and USB ports. Sometimes any combination of things helps
Got it. Rebooting now and starting nothing but RSD Lite. Also gonna change the USB port. (SIM and SD gone as of awhile ago, so no worries there. Thanks for checking though)
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
xyrovice said:
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
Click to expand...
Click to collapse
Glad to hear it worked for you, I know what its like to sh*t bricks over a phone snafu so congrats and welcome back to the land of the living.
Bricks? That may have happened when I flashed Adeo and got the red lights.
This time, I sh*t absolute trains.
And I'm beginning to like the Atrix more and more. I didn't lay down all that I had already done trying to recover my phone when I realized things had gone awry, but I'm sure that, on a software level, it was equivalent to repeatedly napalming a small Hawaiian tiki hut.
Thank you again, my friend. I'm almost done flashing 1.83 at this point, and I couldn't have done it without you guys.
Message to delete
I would think your problem lies in trying to flash US At&t software to your French Orange phone. Go to: http://forum.xda-developers.com/showthread.php?t=1125944 and find the French Orange firmware (there are two of them) and download them. If those don't work, try starting your own thread either here or in Q&A. Good luck!
Tim
It works
Happy
Thanks you

OH NO! Another messed up Droid X

A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?
check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/
It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!
My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community

I need Help - Serious Acting up of Phone

I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.
aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.
live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]
live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.
in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol

[Q] Defy near death or worse. Please help!

Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2

Defy bricked; not responding, need Help!

Hey folks,
before I start describing my fu*k-up let me thank you for all your great work and support in this forum! It makes tinkering with your phone so much fun
Unless you achieve what I have..
Last Rom was the JB buil from Quarx. I was running the build 31.12. and wantend to update to 07.01. This is where I got stuck in a bootloop and started freaking out. I did a lot of random stuff and finally tried reverting to stock to start all over again. I tried doing this via this method here: http://forum.xda-developers.com/showthread.php?t=1807899
Now my phone does not respond at all. When I try to power it up with the Vol+ pressed, nothing happens, same with Vol-
Only response I get is when I plug it in to my PC and start RSD Lite, it shows up as a device, but without any information on the device.
What the hell am I supposed to do now?
Thanks in advance for your help (If there is any hope at all..)
I think this might have to do with the fact that I used the wrong sbf. Which one do I have to use? The last one I flashed was JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTDACH_P025_A008_HWp3_WIG144847_Service1FF
Is there a sbf that will work for sure? I don't need to downgrade afterwards..
I think you need to go MacGyver.
Your battery level is too low so you need to take a usb cord, cut it, expose the wires and connect them directly to the battery.
There are detailed guides with pictures around (I know I had to this once).
Apart from battery which seems to go dead try BL6 sbf. The one you used doesn't allow to flash CM10 2ndboot builds (BL5 Chinese eclair, which caused a lot of troubles).
Regarding battery my proposal would be an external charger or other defy. Doing McGyver you shall do it with caution.
My proposal is 4.5.1-134_DFP-137 retail Nordic from this site - defy+ fROM which causes no problems for most of custom ROMs. Anyway even after the ROM you've flashed there is no way back to froyo.
Try This
http://forum.xda-developers.com/showthread.php?t=1820282

Categories

Resources