Database Users

help! Defy wont boot, white light at top, rsdlite doesnt recognise

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.

[Q] Please help!! can't recover from soft brick, tried lots of methods, Atrix 4G

So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.

Tomn4569 said:
So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.
Click to expand...
Click to collapse
Does it say anything? Does it power off after? Can you get into fastboot or android recovery?
Sent from my MB860 using xda premium

Yeah I can get into fastboot, and android recovery and all that stuff, but i'm not sure but I think I may have deleted the OS(or something like that) and it does turn off after a few minutes

Have you unlocked the phone? Can you get into rsd flash protocol? Might just flash the bootloader unlock and unlock it, after that flash a custom rom. Search for pudding or ihop to unlock.

I can get into RSD protocol, I tried a method on here last night which used RSDLite (this one http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf )
it didn't work though it got to a certain point the said flash failed

Try the script I made here.

Is it suppose to take a while to boot up after flashing a new ROM?
Never mind it failed again...

matthew5025 said:
Try the script I made here.
Click to expand...
Click to collapse
I tried that but now on the phone is just says:
"Failed to boot 2
Starting RSD mode"

If your phone is unlocked. Flash the same exact version u had with this link. http://forum.xda-developers.com/showthread.php?t=1125944
This is an sbf. Download the correct version, install Motorola drivers, place in folder with least file paths ( ie: C:>atrix4g>sbf file ) use latest version of rsdlite or recommended. Follow sbf procedures. I am not responsible blah blah, but this should fix it. Don't panic. I have actually used this when I failed to unlock my bootloader. So in essence, it worked for my locked bootloader. Still, there is risk, try only if u feel comfortable.
Sent from my MB860 using xda premium

[Q] URGENT!!! How do I recover Defy+ after failed 2ndinit install

Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)

which bootmenu did u install?and did u try flashing the SBF file via rsd lite?

fr0dzy said:
I have since read that one should never use 2.0 for Defy+ as it is known to have issues
Click to expand...
Click to collapse
I have run 2ndinit 2.0 on my Defy+ with no problem at all. I installed the latest bootmenu (1.0.7). Do you get the blue LED after powering the phone on?
You could try wiping data and cache in standard recovery. You should still be able to get in to that by holding vol- when you press and release the power button (press vol- and vol+ simultaneously when the android with the "!" in a red triangle appears). Your phone should still be rooted and have 2ndinit in place after a wipe. (Presumably you had rooted the phone? 2ndinit won't work otherwise.)
If that doesn't work then you may need to re-flash the SBF. If you know the build number of the ROM on your you can have a look on this thread to see if there is an SBF for it available online.
As a last resort, you could ask Motorola to fix it. If it's rooted then you've voided the warranty but if all it needs is a ROM flashing then they shouldn't charge you very much to do that. Better spend a few tens of dollars to fix the phone than write it off at a cost of several hundred dollars, surely?

recall while doing the install
did u root first??? did u get superuser permission prompt on downloading 1.0.7?did ur led flash GREEN???ensure that these are all yes

Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.

fr0dzy said:
Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)
Click to expand...
Click to collapse
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..

farsight73 said:
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..
Click to expand...
Click to collapse
+1 for your comment

Same thing happened to me as the OP.
Installed 2ndinit onto my Defy+, said installed and asked to switch off USB debugging and then reboot. I did that and am now in a boot loop. I didn't see the blue led when the phone rebooted, just straight to loop (red M logo, black screen, repeat).
I have tried taking the battery in and out (didn't help), celared cache and also factory wipe/reset (didn't work either). I can get the factory recovery and bootloader, but no android or 2ndinit recovery.
I assume I have to reflash with a full sbf. My question is this -
Does anyone have the stock Defy+ Telstra AU sbf for 2.3.4 (4.5.1-134 DPF-891) or more recent updates?
If not what is closest? I have found a few here but some of the 2.3.4 ones (bl5??) have no links (megaupload etc been pulled) or no root. This one looked promising (here) but no link. Would this one (here) be good?
Can I then apply OTA update to get back to AU firmware if I need? I would use MS2Ginger or CM7 if/when I get the phone working again, but return to stock is still useful.
Thanks for your help,
Nova

i must say u need to flash proper sbf to recover...
just wanna share my experience...
after installing SndndInit v2.0 ( with stock 2.3.6_134 DFP1321 ), i installed stable version of recovery & rebooted my phone...all of this with usb debugging "ON"...n got no errors! maybe there is no need to keep debugging off...
Sent from my MB526 using XDA App

OK, I flashed full sbf and got the phone working again (uses the sbf from the second link in my previous post). Then rooted and install 2ndinit again.
Boot loop again, exactly the same as the first time.
Install goes well, says it is installed, green led is on, however when I reboot, boot loop. There is no recovery screen or anything (except stock).
Is there some more detailed install instructions other than in the 2dninit thread? I have been transferring to sd card root, click apk to run 2ndinit, select 1.0.7 and it says everything worked. Just doesn't when I reboot.
Cheers,
Nova

No-one has any suggestions?
Do I need to put 2ndinit.apk in phone and not sd card?
I am going to try an older version and see if that works.
Cheers,
Nova

i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..

Well I tried v1.7 and that worked. I then updated to version 2.0 and that worked as well so i don't know what was going wrong. The only thing that happened different was the red led came on while 2ndinit 1.7 was loading (this had not happened before), so I would guess that 2.0 wasn't properly installing even though it said that it was installed.
Thanks for all your help.
Cheers,
Nova

hit thanks if I've helped
right now I'm having ICS on my phone thanks to quarx
Sent from my MB526 using XDA

apurvdate said:
hit thanks if I've helped
Click to expand...
Click to collapse
Did that. And thanks again for your help.
Cheers,
Nova

Had exactly same problem
I did the same experience as you after locking up after 2ndInit.
I used your recovery sbf as suggested and the phone works again. Thanks!
Were you able to find a Telstra Defy sbf and were you able to get 2ndInit to work and upgrade to CM9 & ICS?
Cheers,

apurvdate said:
i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..
Click to expand...
Click to collapse
I have rooted phone and tried both the 1.7 and 2.3 apps for 2ndInit Recovery and still on stock ROM but i never get the blue led flashing on boot up.
Any ideas?

Defy Plus indian firmware
nidhish91 said:
Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.
Click to expand...
Click to collapse
Can u please provide me the indian firmware link
Thanks
Zafar

Black camera!
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!
---------- Post added at 06:31 PM ---------- Previous post was at 06:23 PM ----------
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!

[Q] Old Motorola Bravo with 2.1 Update 1 ATT

I have Motorola Bravo with 2.1 Update 1 ATT. Can anyone help me to upgrade it to CM7 from quarx?
I want to know what are the tools I can use to root, install recovery.

anidesh said:
I have Motorola Bravo with 2.1 Update 1 ATT. Can anyone help me to upgrade it to CM7 from quarx?
I want to know what are the tools I can use to root, install recovery.
Click to expand...
Click to collapse
Why dont you upgrade first to froyo?
Connect to internet, go to settings -> about phone -> I dont remenber the next
Else if you can upgrade via OTA update,
http://forum.xda-developers.com/showthread.php?t=1559109
and flash SBF with RSD Lite!
We will continue after you upgrade to froyo!

Thanks
Please excuse me for being lazy. I should have searched more before posting my query. I found your guide of upgrading from Froyo before posting my query.
Anyway... thanks once again.......
I will upgrade to Froyo and then upgrade to quarx CM7 build. [Does wifi hotspot and USB tethering works in quarx CM7 build?]

anidesh said:
Please excuse me for being lazy. I should have searched more before posting my query. I found your guide of upgrading from Froyo before posting my query.
Anyway... thanks once again.......
I will upgrade to Froyo and then upgrade to quarx CM7 build. [Does wifi hotspot and USB tethering works in quarx CM7 build?]
Click to expand...
Click to collapse
Of course, everything is working fine.
You can also use MIUI too everything is working , but I recommend CM7 it has official support from Quarx, ICS CM9 its officially supported.

I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?

anidesh said:
I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?
Click to expand...
Click to collapse
When you install 2init and you run it, you press on install recovery, whatever you want, I always choose lastest.
It will ask you for root permissions twice. Later when installed led notificarion eill show green.
Turn off the phone then turn it on when motorola logo is shown you will see notification light in blue, press vol down button, and thats all.

Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.

anidesh said:
Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.
Click to expand...
Click to collapse
Did you press volume down button when blue light?
It will go inmediatly to boot manager!

anidesh said:
I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?
Click to expand...
Click to collapse
Leave Debugging enabled after 2nd-Init installs and restart.
anidesh said:
Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.
Click to expand...
Click to collapse
Its not SD Card related. Did you update to Froyo with the OTA or SBF? I used the SBF myself and have never had any 2nd-init issues after installing it. One thing you can try is Factory Reset. Turn on the phone holding Power+Volume Up, then press Volume Up+Volume Down on the screen with a green triangle. Then select Wipe Data\Factory Reset. What this does is deletes everything on /data partition; old eclair data may still be there preventing the tools to work properly if you updated with OTA. Sometimes latent data is still left behind after flashing the sbf and this also helps with that as well.
Since you plan on installing custom roms, you can skip the Blur Setup by typing "eebluroffee" on the very first screen after flashing the sbf. Just hold down the menu button and it will bring up the soft keyboard. There's nothing to select to type into, just type the command and it will eventually work. Sometimes it takes a few tries to get it to work. Then just root and install 2nd-Init as usual.
Here is the link to the thread with the latest version of 2nd-Init Defy. The ones on our forum are outdated, but usually work perfectly (always for me).
Updated 2nd-Init 2.3 Thread

Thanks a lot. Finally I am able to install 2nd Init by replacing latest apk in installer created by josuearisty.
Thanks skeevy420 for the hint. Now I am able to upgrade bravo to latest CM7 from Quarx.
Mine is the oldest Bravo (its a engineering sample from Motorola).

anidesh said:
Thanks a lot. Finally I am able to install 2nd Init by replacing latest apk in installer created by josuearisty.
Thanks skeevy420 for the hint. Now I am able to upgrade bravo to latest CM7 from Quarx.
Mine is the oldest Bravo (its a engineering sample from Motorola).
Click to expand...
Click to collapse
If it is an engineering sample, it may have an unlocked boot loader...

marquae11 said:
If it is an engineering sample, it may have an unlocked boot loader...
Click to expand...
Click to collapse
I first though that as well. But if it did, it lost it by flashing the sbf and going retail.
@anidesh -- if you've never, ever, ever flashed an sbf on you're phone can you run the following two commands on Android Terminal Emulator without quotes "su" then "dd if=/dev/disk/mmcblk1p15 of=/mnt/sdcard/boot.img" and upload the boot.img to Mediafire or similar.
If you have flashed the sbf, then don't bother since if you had an unlocked bootloader you just lost it.

I already flashed retail sbf so I lost it. I have one more engineering sample. Its battery connection has problem. If I am able to fix it then I will get image you are asking.

anidesh said:
I already flashed retail sbf so I lost it. I have one more engineering sample. Its battery connection has problem. If I am able to fix it then I will get image you are asking.
Click to expand...
Click to collapse
Have you tried making a MacGyver Cable? Although that won't work if it is a problem with the internal connection.
If it is just a battery connection problem then an OEM Motorola Factory Cable will work -- they send power directly to the phone where the standard usb cable only sends power to the battery. Only problem is they cost around $40 USD. Although if you flash roms a lot they are worth buying since you can flash the sbf and roms with 0% battery. There are sites with mods on how to make one, just google and you'll find one. If I remember correctly, Epsylon3 has a post with a tutorial on how to make one.

skeevy420 said:
Have you tried making a MacGyver Cable? Although that won't work if it is a problem with the internal connection.
If it is just a battery connection problem then an OEM Motorola Factory Cable will work -- they send power directly to the phone where the standard usb cable only sends power to the battery. Only problem is they cost around $40 USD. Although if you flash roms a lot they are worth buying since you can flash the sbf and roms with 0% battery. There are sites with mods on how to make one, just google and you'll find one. If I remember correctly, Epsylon3 has a post with a tutorial on how to make one.
Click to expand...
Click to collapse
If someone wants to try new items to MIUI between this...
link..http://forum.xda-developers.com/showthread.php?t=1535035
skeevy420 as work with the rom pikachu edition

[Q] Defy MB525 - Cant install Any rom without bricking the phone.

Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??

Spersico said:
Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??
Click to expand...
Click to collapse
Try the retail Taiwanese DFP-231.

Thanks!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
Thanks dude, i've made that, but i still have problems, it helped me a lot though, since that in a moment not even one rom of the defy plus worked, except this one.
I keep dealing with the issue, but using this guide, i think i might get to the point that i want (that is... everything except the stock rom).
http://forum.xda-developers.com/showthread.php?t=1889325
Thanks!

I made it!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.

Spersico said:
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.
Click to expand...
Click to collapse
You can use framaroot instead of using the double flash method. See the new CM7.2 by maniac in the dev thread. Try it.