[Q] Defy+ can barely access bootloader, damaged OS, kernel, firmware. - Defy Q&A, Help & Troubleshooting

My defy+ is in agony right now.
Some days ago my CM started misbehaving, losing its settings on reboot.
So I tried flashing another CM, with which I couldn't connect to 3G.
I switched to a Slim rom I had used before, but 3G didn't work either.
So I flashed some other kernel, but I guess I did something wrong, because it booted directly into the bootloader.
I installed the motorola drivers and RSD in some WinXP computer, and flashed "Android 2.3.5 Blur_Version.45.2.500.MB526.Personal.en.AR" from http://sbf.droid-developers.org/phone.php?device=28
Now the screen wouldn't even show the bootloader text, and the charging LED wouldn't turn on when plugged to the wall, only when plugged to the computer.
Then I found some thread that said you could unbrick that kind of brick flashing some .sbf and some firmware file.
I had to McGyver the battery ("battery low, can't program" error) to flash those through RSD, but that didn't help.
Conclusion, my OS, kernel and firmware may need to be fixed, and RSD (I think) can recognize the phone and flash .sbf files,
but I don't know which one to try, and I don't want to screw it up even more.
Any help would be nice, I'll try to give more info if needed.

Related

[Q] Bricked Defy and not recognized by my USB

Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.

Can't access recovery!

OK, so I have a D2 that someone gave me. It was completely stock (not rooted), but had all of their stuff on it still so I decided to do a factory restore through the android menus. The process started and the phone got stuck at the "M" logo, I left it for a few hours, and never budged.
I can NOT get into recovery, holding "X" and power on battery or connected to USB does nothing, have tried about 50 or 60 times now.
I can get to the bootloader and flash a new sbf (tried 2.3.20, 2.2.20, and downgrading the bootloader to d2.35) aside from the d2.37 bootloader I don't know of any other sbf's to try untill the GB one leaks, and who knows when that will be. I am using RSD lite 4.9 on win 7 x64, and 2.3.20 does not error out, also it identifies the phone as "s flash omap..." something instead of A955 or droid.
Sorry for the lengthy post, any help would be appreciated.
Edit: I tried flashing the 2.3.20 sbf from an ubuntu live CD with no joy. I just don't understand, i'm not getting any errors with ADB, it completes just fine, so recovery should be there for me to go into. The better part of 2 days trying to figure this out now.
Just a quick question, is recovery included in 2.3.20 full sbf?
Try it on a different computer. That worked for me. S flash is OK. As long as it says connected, you're good. You need to sbf. As long as you can get into Bootloader (2. 37)you can sbf.
Sent from my DROID2 using XDA App
That was the next thing I was going to try, need to get an OS on my old laptop to try, I have been busy so I should get to that sometime before the weekend. Dug out an old OG Droid that had the same issue that I could never figure out too, and got a custom recovery flashed, but no success on the full SBF or restoring a backup. Hopefully it is just this PC that is not playing nicely.
Thanks for the suggestion.
You can't get into recovery after you SBF? Is that what you mean?
wrichards2009 said:
You can't get into recovery after you SBF? Is that what you mean?
Click to expand...
Click to collapse
Exactly, it's like recovery is not there. Powering up while holding X does nothing, all I get is the "M" logo. I've let it sit and eat a whole battery just sitting on the "M". I will try to flash on another computer or two tonight and post my results.
Well I finally had time to try on another computer, and no luck. Used a freshly downloaded SBF, moto drivers and RSD Lite 4.8. Also I hadn't thought to check the logs before, and the FlashErrorLog has 4 errors, ERROR: AP Die ID, BP Die ID, AP Public ID and BP Public ID.
Everything went same as before, RSD completes with no errors. (well almost completes when I use my Motorola branded cord, stops at rebooting phone, and with my wifes LG branded cord, it reboots into the bootloader automatically, strange)
If anyone else has any ideas, I'm just at a complete loss here, willing to try something drastic at this point.
Having a similar problem, so hope you don't mind me piggybacking on your thread. I'm running 2.3.3 rooted on my D2, and I cannot boot into recovery either, but also can't get SBF to recognize my device on any computer. Any ideas?
How to get into Clockwork Mod
Is there a way to enter Clockwork MOD recovery on a rooted phone Manually? I am away from a computer, phone seems to be bricked need to get into recovery MANUALLY ...................

[Q] Bricked Milestone2? Wont Charge/Stuck at M logo

So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks
viiniq said:
So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks
Click to expand...
Click to collapse
1.Download RSD Lite
2.Download the stock .sbf file for your device
3.Use your friends battery and boot into bootloader by holding Power+Volume Down+Camera button
4.Open RSD Lite, choose the .sbf file you downloaded, connect your phone to pc with usb cable and flash it.
If your pc doesn't reckognize your phone, you'll have to download and install the latest motorola milestone 2 usb drivers.
Ok. So i tried to apply the sbf file, but as soon as the process starts, RSDLite says under the status area "Phone[0000]:Creating Image File." and it wont get thru this. Any ideas?
Maybe try sbf_flash on linux?
Will the sbf_flash work the same on the mac? Or should they work differently on mac and linux? I tried it earlier today and i got stuck at some part i cant remember...I'll recharge the battery with a universal charger that i found (cause it's saying its too low to program) and try it again tomorrow, so i just wanna be sure that i can do it on the mac...
Thanks
It should work same way. OS X version is just port from the linux version.
You have to run RSDlite as an administrator. Right click on RSD.exe or RSDlite.exe not shure what's the exe file named and Run as administrator.
br Zola
having the same problem
after flashed MIUI/CM7
the battery died then the phone cant boot to desktop
tried RSD Lite, flash failed lol
Tried to run RSD as administrator. Still stuck at the same point.
Tried sbf_flash, stuck at 'waiting for phone:'.
I'll try to download the sbf file again, just in case it is corrupted.
Any other ideas?
PS.: I'm running rsd on VMWare, could this be the problem??
Dunno how exactly works USB bridge in VMWare, but rsd on pure (not virtualised) system is worth a try. Also - are you sure, your battery is charged? I know, that if your phone can't boot, the battery will not charge via USB - you should use universal charger or somebody here recommended (and successfully repaired MS2 this way) put contacts directly on the battery to charge it little (just for RSD flash).
I charged it on a charger that you put the battery directly into the contacts. I'm sure that it is charged cause 1) the led display on the charger says so and 2) when i get to bootloader mode to apply sbf, it says 'Battery OK / OK to program' , and before i charged it, it would say: "battery too low, cant program", or something like that.
I'll try to get a windows pc and try to apply the sbf
Thank you guys.
I was trying to flash it with a sbf that was on a pendrive. All i did was transfer the file to the HD and flashed it via RSDLite, using VMWare.
Now my phone is working again.
Thank you very much to everyone that helped me

[Q] Motorola Defy Will Not Boot

I flashed a Defy+ rom (2.3.4) on my Defy (MB525), and it worked great. GPS and location finding, however, didn't work. My idea was to flash back to the stock 2.2.1 and restart to get upgraded to a more stable custom Gingerbread rom. The original issue in doing so was that the flash (WajkIUI) was for the MB 526. I was finally able to flash by changing the USB drivers to the MB526 drivers. Much to my dismay, flashing the stock USA TMobile Froyo through RSD Lite (versions 4.6, 4.9, 5.0, 5.3, 5.6) did not work. It will flash, then note it as a "PASS," then the screen on the phone shuts off. I even tried flashing back to the factory stock 2.1 using the same, but to no avail. My phone currently will not turn on at all, though retains the white LED after the power button is pressed if plugged into my PC. I have tried pulling the battery for a few minutes and using the bootloader, but it will not turn on unless connected through the PC. I noticed similar issues in the following threads, and tried the suggested solutions:
http://forum.xda-developers.com/showthread.php?t=1326683
http://forum.xda-developers.com/showthread.php?t=1011554
Any suggestions would be quite appreciated.
Thanks,
TopoCo
was the battery 80% or more when you started the flashing process? I once flashed my defy525 with 30% and didnt even boot (and it doesnt charge with the charger), i had to do a usb-revive charge to the battery then the flashing process completed.
tpc8dd said:
I flashed a Defy+ rom (2.3.4) on my Defy (MB525), and it worked great. GPS and location finding, however, didn't work. My idea was to flash back to the stock 2.2.1 and restart to get upgraded to a more stable custom Gingerbread rom. The original issue in doing so was that the flash (WajkIUI) was for the MB 526. I was finally able to flash by changing the USB drivers to the MB526 drivers. Much to my dismay, flashing the stock USA TMobile Froyo through RSD Lite (versions 4.6, 4.9, 5.0, 5.3, 5.6) did not work. It will flash, then note it as a "PASS," then the screen on the phone shuts off. I even tried flashing back to the factory stock 2.1 using the same, but to no avail. My phone currently will not turn on at all, though retains the white LED after the power button is pressed if plugged into my PC. I have tried pulling the battery for a few minutes and using the bootloader, but it will not turn on unless connected through the PC. I noticed similar issues in the following threads, and tried the suggested solutions:
http://forum.xda-developers.com/showthread.php?t=1326683
http://forum.xda-developers.com/showthread.php?t=1011554
Any suggestions would be quite appreciated.
Thanks,
TopoCo
Click to expand...
Click to collapse
Hi. I have the same problem, I did something wrong whiles chaging from CM7 to MIUI on my Defy. Now I've lost my recovery mode, and only gets a white lite when I connect the device to my laptop and it says connected after flashing the phone following the thread below:
http://forum.xda-developers.com/showthread.php?t=933710
My phone is now dead. Any help please?
adolphstone said:
Hi. I have the same problem, I did something wrong whiles chaging from CM7 to MIUI on my Defy. Now I've lost my recovery mode, and only gets a white lite when I connect the device to my laptop and it says connected after flashing the phone following the thread below:
http://forum.xda-developers.com/showthread.php?t=933710
My phone is now dead. Any help please?
Click to expand...
Click to collapse
flash a sdf whit rsd lite
can u please specify which kind of sdf file to use for my phone. it orginally came with android 2.3 T-Mobile. MB525
i have the same problem... i tried every sbf.. none of them work
Try o2 sbf
Sent from my MB526 using XDA App
hi i have the same problem ; i hd flash my defy with android 2.3.5 and after that i was flashed with 2.2.1 so in the RSD flash he does not boot no recovery no boot loader but whin i conect it with rsd flash he rite s flash simply
All of you guys had the same problem. You tried to downgrade to a lower BL, which is not possible (try using fixed SBF method). You should understand that once you flash GB, it's not possible to downgrade to Froyo.
Sent from my MB526 using Tapatalk

[Q] Defy is bricked and it won't show up on RSD Lite.

I tried flashing a couple of sbf files on my Defy and I had no issues until I tried flashing the T-Mobile_MB525 file. It did everything on RSD and it said PASS. I can't turn it on. I can't access the boot load screen or the recovery screen. RSD won't show my phone. The only thing I see is a white light from the phone. I need help. I want to go back and flash the original stock rom on my T-Mobile USA Defy.
try post #4
http://forum.xda-developers.com/showthread.php?t=1894069
Check the smg versions of the sbf you Fashed before that one. You will find the needed tools in the Sicky threats.
Could be you flashed one of a higher version before that.
Did you flash with low battery? Could be it was out of juice. But it said pass but I don't know if it means much. Does RDS recognize your phone?
Whenever I connected my Defy to my laptop a white light shows up.
The only sbfs I flashed were the jrdnem deblur the jordan sbf that's the one I use to go back to stock and the T-Mobie_MB525 is the sbf that messed up my phone.

Categories

Resources