Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie
What rom have you been using ? It looks like you have flashed 2.21 or 2.34 while you had had 2.51 before or you was trying to direct downgrade from 2.2 froyo to 2.1 eclair.
Use another sbf for the flash maybe that is the problem
Sent from my MB525 using Tapatalk
choudu1 said:
Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie
Click to expand...
Click to collapse
Make sure you use a compatible boot/devtree loader. Try the 2.1, the 2.51, and the Tmobile 3.4.2-107 available elsewhere on this board.
It's nearly impossible to brick the Defy.
Not to hi-jack the thread - just don't want to start another one for an identical issue. I am running into exactly the same problem though I have the USA version - not UK.
Here is what I did:
To start, I had the stock USA ROM (My wife has the same phone so I can get specific details on stock build after I get home from work, if needed)
1. Rooted with superoneclick
2. Installed Custom Recovery (http://forum.xda-developers.com/showthread.php?t=875233)
3. Installed Milestone Overclock & Overclocked
4. Made backup to my SD Card of current image (using SW from step 2)
5. (On PC) Installed RSD Lite
6. Downloaded 2.34.1 Central Europe ROM (.sbf) and copied into Prog. Files for RSD Lite. Device showed up in RSD Lite so I clicked “Start.” RSD Lite created image, then copied image over – phone display changed to saying “SW Loading” or something like that. When the load finished executing, the phone went to reboot and all I got was the same little white light (up by the presence sensor) that was on steady for the phone – appears to be bricked. I was still able to access bootloader mode last night so I tried flashing other ROMS – (two others to be precise) – but to no avail. Now (next day) I can’t get RSD Lite to recognize my phone – the battery was kind of low so maybe it died and having it plugged in via USB is not charging it?
Un-bricked!
Charlie,
Don't know if you were able to get your phone back yet, 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
basically i it flashes fine. i got a new battery for it. on rsd lite it says "pass" but the phone does not boot i cant get it into bootloader or recovery
I have my phone in similar situation, I was trying to update to Froyo/( KR 3.4.2-72) from stock german eclipse (2.51) and now i am with a white LED when i power on.
I flashed many roms 3.4.2-xxx......and stock 2.51 with RSD lite 4.9, it shows finished but doesnt restart itself, it stays with the white LED.
SWDL.txt shows
04/20/11 02:40:35 000012fc Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:40:35 000012fc Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
and sometimes
04/20/11 02:45:11 00000230 Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:45:11 00000230 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR
Is it because the bootloader is corrupt? or ??
Can someone provide with a defy booatloader? and is it sufficient to flash this loader by rsdlite?
Thanks a lot!! (btw i have enough battery from a friend)
The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App
and use the latest RSD Lite to flash!
Mcdomms said:
The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks a lot! I learnt the above as a lesson!... not on (nearly)stock rom... but after one week of brick like situation. Accumulated some guts.. will try nandroid backup od froyo kr...
Thanks for the help guys. But I took my defy back to cex. They sent it off for repair and apparently they could not fix it so now I got a milestone as a replacement. Well at least now I can enjoy gingerbread on cm7
Sent from my Milestone using XDA App
Related
hey, guys! i was trying to install cm7 on my defy. I had the UK 3.4.3-11 fw on it before, and tried to flash cm6 with rom manager, checked wipe and backup. It backed up my previous rom, but then it rebooted, and now all I see is the notification bar, and a black screen with the text "set-up" on top of it. The touchscreen works (accelerometer too), and the buttons vibrate when pressed but don't do anything else. I tried to flash a new sbf with rsd lite 4.9, and it showed my phone, but couldn't flash anything, because I couldn't press the start button. Any help, please?
I bricked another phone after installing clockwrok mod, it would even boot and I couldn't flash any ROM anymore. Fortunately the shop replaced it under warranty.
On the Defy I used the files posted on this forum and it worked fine.
mine boots. and where are the files posted?
Which sbf did u try and flash?
Sent from my MB525 using XDA App
i tried two. 2.51.1 and 3.4.3-11, both uk and blurred. none of them worked. btw, the 3.4.3-11 was the one i was using before, don't know if it matters or not.
ok, turns out i can receive texts and calls, and do anything that shows in the notification area. i just can't get back to my homescreen, or get the menu to show. worst thing, i can't get to settings, because afaik i need usb debugging to be enabled to flash an sbf, don't i?
Oh okay I was thinking it was a downgradibility issue, but apparently not. Similar thing happened to me and I just kept trying different ROMS And eventually one worked
Sent from my cyanogenmod 7 defy
I dont think its a problem with the roms i wanted to flash, because whatever i did, rsd lite didn't allow me to start to flash.
I had 3.4.3-11 before. After that I tried the nordic ROM and using it I installed 2ndinit and then CM7. I meant the files in first posts these threads:
http://forum.xda-developers.com/showthread.php?t=1037076
http://forum.xda-developers.com/showthread.php?t=1026853
http://forum.xda-developers.com/showthread.php?t=1033654
turns out there's only one sbf i can flash (uk blurred 2.51.1), but when i did, it totally bricked the phone. now it doesn't even boot, the screen remains black, and the notification led doesn't show anything. the pc recognizes it, but the only thing i can do is reflash the same sbf which bricked it... any chance if i bring it back they'll give me a new one?
Im in a similar situation now as well. All im getting is a notification bar and black screen. I was on some chinese rom running jboogies deblurhoney for a while and tried going back stock. Now im trying a bunch of roms with no solution. Ive tried 2 different tmobile us roms, and one orange rom. No success as of yet.
zakoo2 said:
turns out there's only one sbf i can flash (uk blurred 2.51.1), but when i did, it totally bricked the phone. now it doesn't even boot, the screen remains black, and the notification led doesn't show anything. the pc recognizes it, but the only thing i can do is reflash the same sbf which bricked it... any chance if i bring it back they'll give me a new one?
Click to expand...
Click to collapse
When I first got my defy I tried to restore a nandroid and bricked my phone anyways what i ended doing since the phone would turn on but the screen would be all black my best option was just to flash anything that was 2.51 so u can try to download any of the newer released sbf or just try and find your original firmware
EDIT: just make sure to wipe data/cache before flashing
Sent from my Life Proof Defy on CM7
Check the results from the thread I recently made
(my solution was to go into the stock recovery and do a factory wipe)
i can't go into recovery, nor the bootloader, the phone wouldn't start. my computer wouldn't recognize it anymore, so all i've got now is a pretty expensive beermat... i think the last sbf which i flashed is a UK 2.51.1, will motorola buy that their official upgrade software screwed the phone up?
That's what I said because luckily an official update came out. I was another brand though.
You could try flashing it with nordic sbf.
I will send you the link as a PM.
I had the same problem, and it worked for me.
I am having an issue with my phone as well. I had it rooted with clockworkmod. I tried to install CM7 Beta 3 and it failed installation at line 7. So I did a wipe and factory reset and did a backup of my last Nandroid and now it just blinks the Motorloa symbol and I and do nothing.
sikerült?
zakoo2 said:
i can't go into recovery, nor the bootloader, the phone wouldn't start. my computer wouldn't recognize it anymore, so all i've got now is a pretty expensive beermat... i think the last sbf which i flashed is a UK 2.51.1, will motorola buy that their official upgrade software screwed the phone up?
Click to expand...
Click to collapse
szia bocsánat, de sikerült valamit találnod? hasonló cipőben járok én is...
nem, semmit nem tudtam már vele kezdeni, a gép se ismerte fel többet. megpróbáltam visszavinni, de a hivatalos motorola szerviz úgy tűnik megszűnt létezni, a bolt nincs nyitva, emailjük halott, és a telefon ki van kapcsolva... fasza, most itt vagyok telefon nélkül...
Same thing happened to me just that I sped through too many things and didn't take my time to read more threads. Right now all I can get to is a boot loop of the motorola sign. Rooted the phone, had a recovery installed but neglected to realize that i needed to install a 2.2 rom before going to cm7. Need help!!!
Hi there, I'm having some trouble flashing my Defy. Here's what happened:
1) Bought my phone today. Installed a couple of apps (Foursquare, Twitter client, 1 or 2 others).
2) Rooted, then installed 2nd Init. Reboot twice, 2nd Init was working fine, I was able to get into ClockWorkMod Recovery with no trouble.
3) The main reason I wanted to flash a new ROM was to record videos at 720p, using Hancock's ROM 720p port. So, decided to get Barebones v1.5.
4) In the thread, it says: "If Your Coming From An Eclair Build Please Flash The Korean sbf, 3.4.2_74-Stock.KR_BLUR.sbf, Beforehand"
5) Downloaded and flashed the SBF using RSD Lite (already had Motorola's drivers and Android SDK installed, so no trouble here, too).
6) Flash the mentioned SBF with apparently no issues. But, when RSD reboots the phone, it simply shows nothing on the screen, nor does the screen light turns on. It looks like the phone is off, it simply does not boot.
7) When plugged to PC, RSD still recognizes the phone. Tried to flash the SBF again, with the same results (when RSD is flashing the SBF, the screen turns on with the "FW Update - In progress" message). RSD is still recognizing my phone, so I'm still able to flash SBFs.
So, what should I do? It looks like my phone is in bootloader (since RSD is recognizing the phone), but with screen/screen lights off. Should I try another SBF? Is my phone bricked? Thanks for your help!
P.S.: Some useful information: I'm not new to the ROM Flashing universe. Had been flashing my phones since I had a SonyEricsson K550i, at late 2008. Already flashed some ROMs to my HTC Magic, but it has none of these downgrade-locks or any stuff like these. So, I'm completely able to follow instructions on ROM/SBF/whatever flashing, and I'm 100% sure I followed all the instructions correctly.
I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App
mys_721tx said:
I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks for sharing, bro. Got the situation under control here, just flashed an american SBF and got things working. I think I just got a corrupt download or something like this.
on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "
vuhothang said:
on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "
Click to expand...
Click to collapse
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording
In case of stuck in startup
try
Pull battery,
put battery back in holding the VOL-Down until the android pops up...
press VOL-Up and VOL-Down at the same time.
Next screen is for wiping and updating.
Wipe Data/Cache
K3n H1mur4 said:
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording
Click to expand...
Click to collapse
hy..can you please post some screenshots on barebones..thx
I've tried several sbf now. But no one works. RSD lite shows "finished" and "pass", but the Defy stays dark. No reaction on pushing the power-button. only rds lite still recognizes it. any ideas?
The only sbf that works for my Defy is the following one for Defy+ http://forum.xda-developers.com/showthread.php?t=1385868
This means you have flashed a SBF that is not allowing a direct downgrade (flashing another SBF with wrong CG codes => Defy won't boot). Unfortunately at the moment there is no workaround to go back to Froyo or other GB versions that have CG31,CG35,CG39 code lower than 6 and CG47 lower than 3.
This happens wen users are not paying attention to warning messages.
Have you wipe DATA/cache before flash the SBF?
Use the latest driver and RSD.
BL=?
First of all, Hi!
I'll try to go straight to the problem and provide the information needed to identify it!
Problem: My Defy got stuck at M logo after installing a Fixed SFB from the 2.3.3 Android. I used the Fixed SFB provided here by the "Official 2.3.3 Orange GB with MotoBlur" thread.
My phone Android: Untill now, I had a 2.2 Froyo used on Pay's Rom for Defy (last 5.1 Build) installed, with "no problems at all" (besides some annoying bugs).
My phone Hardware: Its a Defy, recently bought (4 months agos) with the green lens camera
What did I do:
(i) Installed RSD 4.9 and Drivers on the PC
(ii) cleared Cache, Memmory, etc etc etc, on the bootloader.
(iii) Installed the fixed SBF on the phone with RSD 4.9
(iv) RSD says it was succesful installed and ask to Manually Power Up the Phone. (It already had turned it on so I left as it was).
(v) After a few minutes (20+), I was still stuck!
(vi) Tried to do all steps mentioned above, with no luck.
(vii) Just restarted the phone annndddd, still stuck so far!
Question: What should I do now to fix the mess?
Thanks everyone!
Updating, I'm downloading again the SBF in case I got it corrupted.
PROBLEM SOLVED, SBF WAS CORRUPTED BEFORE AND NOW WORKED!
Flashed this yesterday morning and it worked great. Decided to downgrade and got stuck in boot loop, so reflashed 2.3 to prevent battery draining, blur would not let me log in no matter how many attempts, via wireless or mobile connection.
ended up reflashing froyo, which logged in first time....
Few days ago I moved from HTC Desire to Defy.
I did root it, installed 2ndInitRecovery. After rebooting I couldnt get defy booted from 2ndInit and ended upu bith black screen. Still dont know why but I uninstalled 2ndinit and ended up stuck on motorola logo, I still can get into bootloader thou.
When tried this solution:
http://android.modaco.com/topic/324...ering-bricked-firmware-on-your-motorola-defy/
RSDLite can see phone connected but there is no info about it (IMEI etc)
and updade doesnt start.
Anyone to help?
if you are on eclair froyo or leaked gingerbd try to set normal boot on sndinit
trouble is that I uninstaled 2ndinit recovery
if rsd can still see it and u can get into bootloader just flash a different rom onto it,i had similar and then flashed the uk 2.2 retail it came str8 back to life!(then i installed CM7...)
miguelsanchez79 said:
Few days ago I moved from HTC Desire to Defy.
I did root it, installed 2ndInitRecovery. After rebooting I couldnt get defy booted from 2ndInit and ended upu bith black screen. Still dont know why but I uninstalled 2ndinit and ended up stuck on motorola logo, I still can get into bootloader thou.
When tried this solution:
http://android.modaco.com/topic/324...ering-bricked-firmware-on-your-motorola-defy/
RSDLite can see phone connected but there is no info about it (IMEI etc)
and updade doesnt start.
Anyone to help?
Click to expand...
Click to collapse
What version of RSD Lite are u using??
I had the same problem no IMEI or other info only N/A when i used the latest RSD Lite problem was solved.
Win 7?
I have been through the same problem and was wondering what os you were using?
I had very little success with win7 x64, I had to get virtualbox and create a win XP virtual machine to make it work.
Also, in order for RSDlite to see your phone, you have to turn the phone on while pressing the volume up button, that'll get you to the bootloader and then RSDLite will see it.
I suggest you use this SBF: JRDNEM_U3_3.4.2_179-002, it is the CEE one and I found it was the easiest SBF to allow custom rom and such (linky)
I hope that helps.
Good luck!
RSD have never seen my phone (i mean model, IMEI etc) but it still worked without any problems
Im using 5.3.1 version. The only info I got is
Bootloader version: v0x000910
Ap Die ID: 18100005cdf767010000dcff0200
Rest of details is N/A
Status: connected.
rak500 said:
I have been through the same problem and was wondering what os you were using?
I had very little success with win7 x64, I had to get virtualbox and create a win XP virtual machine to make it work.
Also, in order for RSDlite to see your phone, you have to turn the phone on while pressing the volume up button, that'll get you to the bootloader and then RSDLite will see it.
I suggest you use this SBF: JRDNEM_U3_3.4.2_179-002, it is the CEE one and I found it was the easiest SBF to allow custom rom and such (linky)
I hope that helps.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestions. Im using xp (had to find one as Im using linux distros). I will have another go.
miguelsanchez79 said:
Im using 5.3.1 version. The only info I got is
Bootloader version: v0x000910
Ap Die ID: 18100005cdf767010000dcff0200
Rest of details is N/A
Status: connected.
Click to expand...
Click to collapse
As long as the phone shows up in the device list on RSDLite and that you can put your Defy in bootloader mode, you should be good to go.
RSDLite never gave me accurate details about the phone when I had these issues but I was always able to flash SBFs.
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
If you try to download from a GPRS or 3G network, disable the download from wi-fi only tab from settings and data management.
miguelsanchez79 said:
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
Click to expand...
Click to collapse
Allready signed out of google talk and then sign in again?
miguelsanchez79 said:
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
Click to expand...
Click to collapse
Go to recovery wipe cache/data
Sent from the Nerd Herd using Tapatalk
Go on the CM7 thread. End of first post and download the latest google apps from there, reboot in custom recovery (CWM recovery or SndInit recovery) and flash the zip.
Re. your bootloop problems:
did you turn off usb debugging after installing Sndinit and did you reboot 2 times (1st boot --> normal then 2nd at blue led, volume down?) ??
If you would have followed the FAQs of CM7, you would have had no such problem....
Hi Guys,
Since I cannot yet post at Home > Motorola Defy > Defy Android Development > [JB] CM10 Android 4.1.1 for the Defy(+) i am posting here.
I was running CM9 on my Defy+.
I tried to upgrade to the 0828 JB for Defy+ and ended up with
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
How? I can't remember.
but every time i use the bootloader and try to load the JB file it says \:
E: failed to verify whole-file signature
So by my understanding i need a custom bootloader as before. (i can't really remember how i loaded the ICS).
Help!!!!!!!!!!!!!!
Regards.
You need to flash a full sbf now to get it back up and running. Have you ever done that?
This bootloader error is a result of flashing the wrong version, are you sure your phone is a DEFY+ and that you flashed the DEFY+ version?
Anyway, just tell us if it's DEFY+ (MB526) or DEFY (MB525) and we will tell what you need to flash to get it back up and running. I hope you do remember that
MB526 Asia Retail SBF
niksy+ said:
You need to flash a full sbf now to get it back up and running. Have you ever done that?
This bootloader error is a result of flashing the wrong version, are you sure your phone is a DEFY+ and that you flashed the DEFY+ version?
Anyway, just tell us if it's DEFY+ (MB526) or DEFY (MB525) and we will tell what you need to flash to get it back up and running. I hope you do remember that
Click to expand...
Click to collapse
Its a defy+ . I downloaded the required sbf but no idea on how to install.
I got as far as Android System recovery (3e) but under apply update from sd card i can't see the .sbf file!!!
help help help !!!!
CHARGE PHONE BATTERY ABOVE 80% BEFORE PROCEEDING......
Requirements
Get the SBF you want to flash
- Full SBF: No Nandroid backup needed, always keep CG versioning in mind.
- Fixed SBF: You might need a matching Nandroid Backup.
Get and Install RSD Lite v4.9: There are reports of other versions working, but this one is what I have used.
Get and Install Motorola Drivers [32bits] [64bits]
Now to Business:To Flash full SBFs, here is the standard procedure:
Open RSD Lite: Click on [ … ] Button and select your .SBF (Remember to rename to a short name and put it on root of your PC) and click Open.
Boot your phone into Bootloader Mode (check last section if you don’t know how to do it).
Now connect your Defy to your PC
The START button on RSD Lite should be available now, click and wait.
How do I enter Recovery Mode?!: With the Phone off press VOLUME DOWN then, while still pressed, power up the phone and leave VOL key pressed until you see a Yellow triangle, once you see this you are in Recovery now press Vol Up and Vol Down at the same time (if you are in Froyo) and the menu will appear, if you are on Éclair the menu should appear without having to press anything.
How do I enter Bootloader Mode: With the Phone off press VOLUME UP, then while still pressed power up the phone. Keep the Vol key pressed until a black screen with some white letters appear. This is the Bootloader.
After Upgrading to Froyo my Defy is laggy, slow or reboots: (!) This is a common issue when coming from Eclair to Froyo. If this happens to you, just do a full wipe (Delete Data/Delete Cache on Stock Recovery), after that your phone should work correctly.
Need - MB526 SBF - Asia Retail 1321 Multilanugage 3.2.6 - Not China!!
Thanks so much.
It worked so far as the loading of SBF is concerned (RSD Lite v5.7 - used it last time , had forgotten)
Only, now the phone will not boot. The screen remains blank/black (not a flicker). Connecting to the USB powers on the White LED. thats all.
Thankfully RSD detects the device still.
The sbf I used was:
DEFYPLUS_U3_4.5.1-134_DFP-1321_CN_SIGN_SIGNED_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P014_A026_HWp3_Service1FF
@ http://sbf.droid-developers.org/umts_jordanplus/list.php
I need the GB 1321 Asia Retail MultiLanguage Version (2.3.6) . (I had this when I moved over to CM9)
The one mentioned above is Chinese I guess. Tried twice with it but no luck
Any possibility of getting the right one? or some SBF that will work??
Pleaseee
Outwitted and outsmarted.. by Android!!!
DEFIER said:
Thanks so much.
It worked so far as the loading of SBF is concerned (RSD Lite v5.7 - used it last time , had forgotten)
Only, now the phone will not boot. The screen remains blank/black (not a flicker). Connecting to the USB powers on the White LED. thats all.
Thankfully RSD detects the device still.
The sbf I used was:
DEFYPLUS_U3_4.5.1-134_DFP-1321_CN_SIGN_SIGNED_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P014_A026_HWp3_Service1FF
@ http://sbf.droid-developers.org/umts_jordanplus/list.php
I need the GB 1321 Asia Retail MultiLanguage Version (2.3.6) . (I had this when I moved over to CM9)
The one mentioned above is Chinese I guess. Tried twice with it but no luck
Any possibility of getting the right one? or some SBF that will work??
Pleaseee
Click to expand...
Click to collapse
tried many SBFs for DEFY+. All end up with a pitch black screen . Power button does not seem to boot Android.
The power button works though as while being connected to USB and White LED on, pressing Power button disconnects the device from RSD Lite.
I am at my wits end. is my Device Bricked for all times?
Quick recap on how I reached this point.
1. Rooted the Defy+ (2.3.6 Asia Retail Multi Language)
2. Installed CM9 (was on ICS for two months)
3. in boot loader installed JB (0828). Before that the Kernel link provided alongside on CM10 instructions. Wiped cache/Dalvik.
got this:
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
4) I did something further like a factory reset (cant remember )
5) Since then the bootloader gives me : Android System recovery (3e) not the other bootloader.
6) Flashed SBFs to try get the GB up and running atleast. End up with no show on the screen.
(though the "SW Updating.." prompt comes thru RSD Liet on the defy screen, so the display is working)
Can even find the right SBF now.. please help. Am desperate for now.. no other handset
DEFIER said:
tried many SBFs for DEFY+. All end up with a pitch black screen . Power button does not seem to boot Android.
The power button works though as while being connected to USB and White LED on, pressing Power button disconnects the device from RSD Lite.
I am at my wits end. is my Device Bricked for all times?
Quick recap on how I reached this point.
1. Rooted the Defy+ (2.3.6 Asia Retail Multi Language)
2. Installed CM9 (was on ICS for two months)
3. in boot loader installed JB (0828). Before that the Kernel link provided alongside on CM10 instructions. Wiped cache/Dalvik.
got this:
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
4) I did something further like a factory reset (cant remember )
5) Since then the bootloader gives me : Android System recovery (3e) not the other bootloader.
6) Flashed SBFs to try get the GB up and running atleast. End up with no show on the screen.
(though the "SW Updating.." prompt comes thru RSD Liet on the defy screen, so the display is working)
Can even find the right SBF now.. please help. Am desperate for now.. no other handset
Click to expand...
Click to collapse
If you're able to enter android stock recovery , do a full wipe/factory reset and reboot your phone...after flashing an sbf thru rsd lite
Sent from my MB526 using xda app-developers app
DEFIER said:
tried many SBFs for DEFY+. All end up with a pitch black screen . Power button does not seem to boot Android.
The power button works though as while being connected to USB and White LED on, pressing Power button disconnects the device from RSD Lite.
I am at my wits end. is my Device Bricked for all times?
Quick recap on how I reached this point.
1. Rooted the Defy+ (2.3.6 Asia Retail Multi Language)
2. Installed CM9 (was on ICS for two months)
3. in boot loader installed JB (0828). Before that the Kernel link provided alongside on CM10 instructions. Wiped cache/Dalvik.
got this:
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
4) I did something further like a factory reset (cant remember )
5) Since then the bootloader gives me : Android System recovery (3e) not the other bootloader.
6) Flashed SBFs to try get the GB up and running atleast. End up with no show on the screen.
(though the "SW Updating.." prompt comes thru RSD Liet on the defy screen, so the display is working)
Can even find the right SBF now.. please help. Am desperate for now.. no other handset
Click to expand...
Click to collapse
Can't believe it.. it worked
http://sbf.droid-developers.org/umt..._USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
Closed for now.!!
I had the same problem, I followed this post:
http://forum.xda-developers.com/showthread.php?t=1542956
I flashed this sbf first:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
And after this rooted sbf:
4.5.1-134_DFP-231_CN_Rooted_SBF
Good luck!