Bricked or not ? - Defy Q&A, Help & Troubleshooting

I was running my defy on cm10 then found a cm10 ready sbf to update, and then it gave me "bootloader 9.10 err:A5,70,39,00,27" so i found my original sbf and flashed it and I got a blank screen(no backlight even) but the phone shows on RSDlite as connected and I can reflash another sbf, and it shows the progress (and sw updating on the phone) then the same blackscreen (with white led on)
So did I cook my phone or am i missing something, thanks for help in advance !

Defy with what kernel on CM10?
Is it redlense or greenlense?
Sent from my sending thing (copyright by domini99 )

what base sbf did you use on cm10? what kernel? what sbfs did you flash after that? does the white led light up when connected to rsd lite?
please give specific information when asking for help, otherwise its like telling a doctor on the phone: "i have a headache, heal me!"...

I was using this sbf base: JRDNEM_U3_3.4.3-36-1.1 ,
with froyo kernel(by epsilon) and epsilons cm10 nighlties(my phone is red lens, although the app which shows the color shows as green),
then i applied this cm-10.Quarx(17.08).Defy+.red.bl4-5.fixed (i have no idea what i'm doing xD) and then i got the bootloader error.
UPDATE: i got it to boot and its working fine but apparently i flashed a defy+ rom(DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed) because it shows as mb526 wtf ? , and if i try to flash gb kernel i get back to the lovely bootloader error(cm10 is now working without the kernel )

Vcek said:
I was using this sbf base: JRDNEM_U3_3.4.3-36-1.1 ,
with froyo kernel(by epsilon) and epsilons cm10 nighlties(my phone is red lens, although the app which shows the color shows as green),
then i applied this cm-10.Quarx(17.08).Defy+.red.bl4-5.fixed (i have no idea what i'm doing xD) and then i got the bootloader error.
UPDATE: i got it to boot and its working fine but apparently i flashed a defy+ rom(DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed) because it shows as mb526 wtf ? , and if i try to flash gb kernel i get back to the lovely bootloader error(cm10 is now working without the kernel )
Click to expand...
Click to collapse
i love it when people do things they have no idea of, and they get surprised when they brick the phone and then beg for help on xda... -.-
first of all, read this thread, so you know what you have done and why it was stupid.
second of all, if the app shows you have green lens (soc module), then it is right.
and third, if you flash an mb526 sbf, of course everything recognizes it as mb526... and because you have an mb526 now (probably without any working camera, because you have green lens), you dont need the gb kernel no more, because you already have it.
funny, right, doing things that you dont understand? now you have made yourself a phone without camera...

My phone is red lens(i think apps read info from kernel), and the camera is working fine on cm10 now although i have done an unnecessary update to cg version(atleast what i think it is),
currently im trying to fix the following problems:
1- Most apps cant detect MEDIA on my sd although i can browse it on all file explorers (EDIT: Fixed itself after another re-install)
2- compass is gone crazy(EDIT: found out this is problem with cm10)
I don't why you're getting so aggressive on me, you have no idea how many times i've read all the guides (im not a dev, im just a poweruser)
i'll be glad if you helped

Related

[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] Can i flash DEFY+ rom on DEFY

I have DEFY(Green Lens).If i flash stock DEFY+ rom on DEFY, what issues will i face other than camera and battery issues. Will i be able to flash froyo sbf again and go back to froyo.
if you flash defy+rom your camera wont work. and do not use sbf.it will update the bl version and it will be difficult to go back to 2.2
Sent from my MB525 using xda premium
Battery wont be recognised and you won't be able to charge the device unless you flash a patch.
Sent not from your device!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Don't flash Defy+ sbf on Defy. It will become a mess. You can't downgrade is not that easy so don't try.
What if that has been done? And why the phone reboots when cold?
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
luweitest said:
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
Click to expand...
Click to collapse
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
hotdog125 said:
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
That's what I have done; it seems I have to try those Defy+ SBFs until find a one that suites for Defy.
solved
I struggled through finally. After I flashed CyanogenMod 7 stable, cm-7.2.0-jordan.zip, the phone does not reboot at low temperature again. Before that I flashed a modified BL5 JDGC_2.12.0.sbf from other sites. I can't imagine why other ROMs will cause low temperature rebooting, but anyway the phone now works in winter and I am happy! :victory:
HELP
I apologize for flooding.
Dear doctors, I need your help VERY!
The problem is this: Download Firmware "CM10 (18.11 + fixBlue). Sbf" decided to ask ..
Turned off the phone, turned on while holding the top of the rocker gromkasti through RSD sew phone, at the end of installation, the phone asks him to reboot manually, generally overloaded, nothing should be loaded, worked the battery, the identity thing, then threw this thing, after a while the phone stopped included at connection to a computer white LED lights up, and the sound came from the connection on the PC .. decided to postpone until the phone as he waited for the new display and touch screen, just 3 days before receiving parts, decided to try to flash .. diode zagoraetsya only when connected to fraction of a second, and gave sound on the PC. Now the identity thing, not only delivers sound on the PC .. and not simply vklyuchaetsya (bought a frog, thought battery low, etc., loaded it as it is .. and no results ..
Doctors ask for your help regarding my vostonavleniya Defayki ..
ps Tried different Mutko with USB, battery and buttons, nothing pomaglo (RSD does not see (sorry for the google translate

[Q] Yet another idiot who bricked his Defy+

Hi all,
With this first post of me, I'll give you something to be warned with what can happen to YOUR phone I'm sorry I have to start a new thread for this, but I can't find a solution elsewhere.
So, my Motorola Defy+ refuses to boot, I can't even get to the bootloader screen. I can still connect it with RSDlite, sometimes a white LED burns when I connect it to my PC. I can flash it and it says "SW update in progress...". But after flashing it still doesn't boot
This is how I got here:
- Bought a shiny new Defy+ (Vodafone Germany)
- Flashed it with an Android 2.3.6 SBF (I don't know details about it, but I still have the SBF-file)
- Was happy with the phone, and made a grave mistake:
- Tried to flash this SBF: DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR because it was recommended for the Nothing But Speed ROM
- And........ The phone got in a coma and couldn't boot up anymore
I know there's nothing wrong with the battery, because it still has a constant 3.8V output. It is actually a little difficult to connect the phone with RSDlite, so I use (the hotwire-fix from Sorensiim).
You are my hero if you've got a solution for this
I don't want to send it to a Motorola service point, because the service point here in the Netherlands has a lot of bad reviews.
Thanks in advance!
The solution maybe simple, have u tried to the latest 231 SBF, cause i guess your Defy+ have CG7 (Bootloader 7) and you flashed 132 its BL6.
So your Defy+ will boot in a black Screen if you flash a SBF with a lower BL.
Thanks for your answer, I'll give it a look.
I'll report soon!
[SOLVED] Yet another idiot who bricked his Defy+
Oh my god, thank you so much!
I flashed it with this SBF: DEFYPLUS_U3_4.5.1-134_DFP-231_VFBLUR (I can't post a link right here, because of spam control. But search for it on sbf[dot]droid-developers[dot]org/umts_jordanplus/list.php) and it worked
You're my phonesaver, you know. And maybe your post has helped others.
Thanks a lot!

[Q] Please help! No booting after flashing a SBF with RSD lite (SOLVED)

Hello,
I know there are some similar threads, but the solutions given don't seem to work for me.. I really hope somebody could help me here.
History:
It's a green lens defy, that first came with Eclair. I had to send it in once and it came back with Froyo, which was slow and annoying from the start.
I wanted to get quarx CM10 (Android 4.1) on it. To do this, I followed the video guides by "locslikes" on youtube (can't post links). First I rooted the phone, then on the video "MOTOROLA DEFY UnBrick Restore to Default SBF" we have been following the xda thread "Is your DEFY / DEFY+ bricked??". It links to a list of sbf-files, and I wasn't really sure which one to take. So I just took one that seemed appropriate. Later I tried some others, so I'm not really sure which one is flashed right now. I tried those marked "retail Germany" or "(provider name) Germany". RSD lite 4.9 does the flashing without any problems and gives me a "PASS" in the end. I tried the SBFs called "JRDNEM_U3_2.21.0", "JRDNEM_U3_2.34.1", "JRDNEM_U3_2.51.1".
Now the problem is that the defy doesn't boot at all. I can't get into the bootloader or anything, there is just no reaction from the power button. When I plug it on my computer, the white LED goes on and RSD lite sees my phone. I can flash other SBFs and while the flashing is happening, the defy screen works and gives me the message "updating...". However, when it is done, again no booting is possible. I do not get a Motorola logo or anything, nothing happens.
How can I go back (or go forward to CM10)?
Please help me, I would appreciate it so much.
Regards
Philipp
it seems like you have to send your phone to repair service again, this issue seems to be with the bootloader has been corrupted and you wont be able to solve it yourself, it needs some very high skills and riffbox hardware flasher with jtag which is really difficult
I was able to boot it up again... this SBF-file did the job for me:
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYOO2DE_P021_A010_HWp3_Service1FF.sbf
I just kept trying lots of different SBFs and that was the solution....
Sorry for bothering you
Please provide the link for that file ...
Hey i been searching for a good SBF file for my Motorola defy MB525 ... every SBF i been trying to flash did not work/ boot but only one i came across which is not stable i.e. JORDN_U3_97.21.51.rar well .. i'll b much obliged if u provide me the link (with spaces) n help me out buddy. you can send the link to this address > [email protected]
Feomatar said:
I was able to boot it up again... this SBF-file did the job for me:
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYOO2DE_P021_A010_HWp3_Service1FF.sbf
I just kept trying lots of different SBFs and that was the solution....
Sorry for bothering you
Click to expand...
Click to collapse

Unable to root Defy MB526

I have Motorola Defy MB525 which recently got BRICKED and I was unable to flash any SBF files found on forums or internet, so I gave a try to MB526 Stock SBF and it worked and my MB525 is now showing as MB526 in "About Phone"
But I am unable to root the device now, none other SBF works too and also few things like Camera, WIFI are not working...
Can anyone help me to know how can I root my MB526(previously MB525) and install custom ROMs or if I can go back to MB525 again???
Why not just be happy that you got your phone back? Why again start to torture it? after rooting you will force it to do things your way(that it knows it cant do). Last time it gave up it's life trying to do something that'd content you.
Ok for rooting, no one does it better than kingo app. It roots any phone model any firmware (the last time it could root my preordered handset just after it arrived).
Download it from kingoapp(dot)com and install it. Enable usb debugging in your phone. Run kingo app, then connect the phone to your pc using usb data cable. Let the drivers install and in case they are not found in your phone, kinggo app will automatically find and download it from the internet(you have to particularly trust it with that. I was made to believe it has a driver database as large as the universe because of the varied and very unpopular models I could root with it; and the drivers were very accurate). Wait for the drivers to be installed and then click on "root" and again wait until it says "rooted successfully." (Trust me it will say!)
thank
thanks a lot... it worked like a charm.... :good:
developeryamhi said:
thanks a lot... it worked like a charm.... :good:
Click to expand...
Click to collapse
I told u :thumbup:
developeryamhi said:
I have Motorola Defy MB525 which recently got BRICKED and I was unable to flash any SBF files ...
Click to expand...
Click to collapse
I don't believe you, you can flash any SBF..but perhaps the defy won'7 start afterwards
If defy shows a black screen there is a problem with the bootloader, if there is a boot loop a factary reset would help..vol(-) on start and vol(+) AND Vol(-) when android is smiling at you.
Anyway, I did the same and flashed a MB526 SBF, just for a try. And it looks that there is no way back due to bootloader trouble.
No problem, you can use a 2ndboot ROM and everything will look shiny.
For rooting I used framaroot, easy and simple, no drivers, nothing.
USB dubug afterwards for Sndinit...
bianchifan said:
I don't believe you, you can flash any SBF..but perhaps the defy won'7 start afterwards
If defy shows a black screen there is a problem with the bootloader, if there is a boot loop a factary reset would help..vol(-) on start and vol(+) AND Vol(-) when android is smiling at you.
Anyway, I did the same and flashed a MB526 SBF, just for a try. And it looks that there is no way back due to bootloader trouble.
No problem, you can use a 2ndboot ROM and everything will look shiny.
For rooting I used framaroot, easy and simple, no drivers, nothing.
USB dubug afterwards for Sndinit...
Click to expand...
Click to collapse
I was able to go to bootloader only and I was able to flash SBFs but none were working, after flashing there was no output, no Motorola Logo or anything, just charging white led was on...
todopertin said:
I told u :thumbup:
Click to expand...
Click to collapse
the only sbf that worked for my phone is DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf
but camera shows black screen, wifi restarts constantly
is there any better SBF i can use??? or any other way around??? as when i tried to install custom cm7 rom, i get some error about update_binary
developeryamhi said:
just charging white led was on...
Click to expand...
Click to collapse
even that LED I missed..no reaction, RSDLite didn't recognized a device
Battery out, VOL up and batt in was the solution to get it recon again
developeryamhi said:
the only sbf that worked for my phone is DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf
Click to expand...
Click to collapse
I used DEFYPLUS_U3_4.5.1-134_DFP-188_TMOUK_SIGN_....sbf 'cause I had trouble starting up without SIM with some SBFs.
Nevertheless, Wifi probs and missing camera iare features when running MB526 ROMs on a MB525 device unless you decide to use a custum kernel.
For ex. Quarx's Cyanogenmod 10 will work fine and some others which work with SndBoot !!! feature.
Please look for a ROM suitable for Defy AND Defy+!
developeryamhi said:
the only sbf that worked for my phone is DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf
but camera shows black screen, wifi restarts constantly
is there any better SBF i can use??? or any other way around??? as when i tried to install custom cm7 rom, i get some error about update_binary
Click to expand...
Click to collapse
that's because you are using ROM/firmware of a different model, there's little you can do if you aren't such a serious developer....try to find a custom rom for your device rather than using the original firmware of an other model. Or simply maybe it's time to buy a new phone.

Categories

Resources