Database Users

[Defy] Stuck at Bootloader 09.10 - Err:A5,69,4E,00,41

I think the title kinda explains for itself!
From what I started and where I got?
Well, firstly, I tried to install 3.4.3-11 Motorola SBF with fixed Blur provided this link:
"Here you are, buddy
Fixed.SBF plus Nandroid of 3.4.3-11
http://www.multiupload.com/PB10JC9NQV"
(http://forum.xda-developers.com/showthread.php?t=966537&page=7)
I moved to the older PC still running Windows XP to manage RSD Lite 4.9 to work and recognize my Defy. (it apparently worked)
After wiping all data and cache, I started the phone in boot loader mode and tried to use RSD to load the SBF.
Everything seemed to be fine. But.....After RSD finished the update, it said for me to "turn on my Device". Well, it was already on and stuck at Motorola Logo.
I waited for quite some time, took a shower, smoke a cigar.... And, when I came back, nothing, phone was still on moto logo.
I force restarted the phone removing the battery. Still got stuck at moto logo for quite some time.
Sooooo, I decided to wipe everything again and try to install the SBF again, this time with the one provided by "Pays Rom" thread.
That was when stuff got bad.
After that, I got stuck at Bootloader with a "error code" indication.
Alright, it was time to read some more cause I realized I fked something up! Then, I find out I could load a Devtree SBF and that would unbrick the phone being able to install another SBF.
No succecs, eventhoug I tried to load those previous SBF, I still got problems either with RSD Lite or got stuck at bootloader with a that "error code" problem.
As I didnt know what else to do, I loadead back the devtree and got that different error code on the phone. (one mentioned on the thread title).
And, this is pretty much my whole problem! lol
Any Ideas what should I do?
My Defy is from Brazil - Claro and was running 2.1 android at the beggining!
Tyvm!

it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.

oct307 said:
it seems like we get the similar Err,my defy also stuck at bootloader Err,my Err code is a5 69 35 00 27,if you have solved the problem,please tell me something about it.
Click to expand...
Click to collapse
Nothing yet.
Still trying to boot anything in it. If I ever find something, I'll let you know!
I'm getting this error now on RSD Lite when trying to load the SBF 3.4.3-11
Failed Flashing process. Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Adress: 0xB2383000 Command: ADDR (0xE023203F), phone conected
New error code prompted on Bootloarder:
Err:A5,70,39,00,27
Now it shows Motorola logo for a few seccconds.
Stuck at code 39 or smthing while trying to install another SBF (the one with PAys Rom)
Ok, it unstucked, now RSD shows "restarting" and the motorola logo is on screen.
Finally, it loaded.
I used Pays Rom after a few tries with the first fixed SBF and jumping to the Pays Rom SBF.
After sometime, it installed!!!!!
The phone just started!!!!!
How about your problem mate, wich point are u at?

To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.

pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
Thank you!
I managed to find that out by myself, but thanks for the help!!
I noticed it was a not downgradable version, but I don't really care as it fits what I was aiming and I don't have any intetions of going back to 2.1!

pomah said:
To solve both of your problems:
download and install the original 3.4.3-11 sbf, no nandroid or anything else.
You should allways be able to get into the original motorola boot loader and from there install any of their SBF, but some of the sbf versions with android do not allow downgrader, therefore you should be sure to use the same version and not a lower one.
Click to expand...
Click to collapse
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode

hello,
I also have a similar problem, stuck on the bootloader but I have the "low battery cannot program" error. When I try to charge the battery, the battery appears with a "?" inside...
Does anyone already get this problem ? Battery out of order ? software problem ?

Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk

lanfearxt said:
Use the macgyver method with usb cables. Search the forum and be brave. I had the same problem
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
this is the post: http://forum.xda-developers.com/showthread.php?t=892026&highlight=battery+charge

thanks for the link
it will help me saving my defy....

oct307 said:
thank you very much!
i have used 3.4.3_11-Stock._BLUR.sbf，but it doesn't work!it's still be stuck at bootloader 09.10 Err:a5,69,35,00,27.
i don't know what's the meaning of the errcode
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?

try this
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.

slayps said:
try apply this Full SBF 2.3 orange http://forum.xda-developers.com/showthread.php?t=1106375
or
2.1 SBF http://and-developers.com/sbf:defy
this is is a sign error in someone codegroup.
Click to expand...
Click to collapse
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files

renatojf said:
I tried a 2.1 SBF and it gave me a black screen.. the phone turns on, but keeps black.. so I re-flashed with a 2.2 sbf and got back to the same error..
Now I'm downloading the Orange 2.3 sbf file.. I dunno if it will work because I already tried 8 different sbf files
Click to expand...
Click to collapse
I'm having this same problem.. anyone successfully fixed this?

neozhu said:
I'm having this same problem.. anyone successfully fixed this?
Click to expand...
Click to collapse
1) Try flashing on different PC to start fresh.
2) If you'd flashed so many sbf. You might not be able to remember them all. My guess is that you might be at froyo state(corrupted/failed system code), thus flashing another Eclair 2.1 sbf would not solve your issue. You must try on Froyo sbf only starting from bootloader mode and rsdlite 4.9 or 5.0.
3) Take note of your battery level as it might draining down while you attempting to put some resuraction on the device.
4) Try relax and take a bath and smoke a bigger cigar just like the OP of this thread did...

i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.

JDM-Bb said:
i too have this same problem, exept i dont know what ver i had and i flashed so many sbf. ive found some sbf that work but i get no signal.
Click to expand...
Click to collapse
no signal..? have you try baseband switcher application..?

yes ive try that with no luck.

hELLO
Please, tell me how to solve that problem with bootloader error A5, 70, 39,00 27 in my defy?? You have said you solved it. please help

you need to be calm and cool with lot of patience. It takes upto 10 - 15 Minutes...
the flashing happens at the speed of your computer.
try to use original cables and use USB ports of your desktop motherboard or laptop without any extension cables.
keep your pc in NO SLEEP mode. Batter should be almost full before flashing ...these are some tips...

DEFY Becomes DEAD After Flash-- Help

My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.

cute_kayani said:
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
Click to expand...
Click to collapse
I think I got the answer for you......
Use below mentioned steps and share the outcome:
1. Download the compressed SBF and extract using any software like 7zip or something - http://www.mediafire.com/?s3uc8cb782w1oue
[Note: Do not use any download manager while downloading.]
2. Use RSD Lite to flash the phone with the SBF file;
3. After flashing let the phone boot up and hopefully it will resolve the issue.
However if the phone is still in boot loops then try entering Stock recovery and wipe data/format and wipe cache also.
Please use the above steps and share the outcome.

ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,

cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!

okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do

pranks1989 said:
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
Click to expand...
Click to collapse
I understand your concern and I appreciate your comment however, I would like to point this out that this firmware is for "India, Indonesia, Malaysia, Philippines, Thailand, Vietnam" and its safe to flash I have flashed it multiple times and its Rootable and even my flash is healthy.
You may visit this link and Control+F "JRDNEM_U3_3.4.3-33-1":
http://and-developers.com/sbf:defy
The chinese firmware which is suspicious of burning flash is "China - JDGC_U6_0.26.0" [Correct me if I'm wrong.]
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
cute_kayani said:
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
Click to expand...
Click to collapse
You may use this firmware or any different firmware from this link : http://and-developers.com/sbf:defy
The ROM which I have given you link is Rootable however not down-gradable.
You may refer this extract from All-in-one-Guide-for-Defy
SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.6, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
ATTENTION: This CG 7 Version is NOT rooteable. You wont be able to flash a lower version ROM nor Root to use CWM.
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
Official SBFs
Here is a list of all the OFFICIAL SBFs, meaning they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
Ref == http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
The only thing which is important here will be to use a Froyo or newer version SBF.

Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now

cute_kayani said:
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
Click to expand...
Click to collapse
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!

Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now

cute_kayani I think you double posted mistakenly....
Have already answered your query above
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Click to expand...
Click to collapse
---------- Post added at 09:26 PM ---------- Previous post was at 09:12 PM ----------
One important thing for your information is the reason behind those black screens was that you must have flashed Froyo SBF before; which was not down-gradable and now at this point you were trying Éclair which resulted in this issue.
So, the Downgradibility of your previous flashed SBF was causing this issue.
Now, as you have flashed this Froyo SBF; so, now onward in case you need to flash you phone you need to use SBF which should be Froyo or newer and must have “3.4.3” or later Build Numbers.
Hope this helps someone who needs this information.

okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.

cute_kayani said:
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
Click to expand...
Click to collapse
LOL its official Froyo it might have more bugs

haha okay i am moving to miui.... but from past 7 days my defy remains dead due to Miui weekly rom update
hopefully this time miui wont make any problem

LOL
All the very best this time ..
You know what last week I also updated to MIUI 2.3.23 and my wifi was not working with that ROM however, it was working fine with my CM9 as I had dual boot.
Please update me if you also face this issue with the MIUI 2.3.30

currently am on 2.3.23 every thing is okay, and wifi also working now am updating it to 2.3.30. will tell you if there any wifi bug.

Will wait for your review!!

More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.

cute_kayani said:
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
Click to expand...
Click to collapse
Lol 2GB internal memory occupied
Yesterday night I flashed with MotoGinger III for a change... so far so good. However, AutoWifi fix is resetting my wifi pwd every 15 mins or so ..

Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.

Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.

mb525 bootloop help please

I have b
een trying for 3 days now to get a MB525 working. I have read hundreds of posts and followed tutorials with no luck
Please can someone help?
Phone powers on to animated moto blur logo, then repeats this 3 times but much faster. It then shows a t-mobile logo for about 15 seconds before going dark, then rebooting and looping.
I have tried wipe/reset from menu.
I have tried flashing 6 different sbf using RSD Lite v5.6 but flash files towards end with verifying checksum errors
RSD Lite doesnt display any details when i click show device, but under the 'model' heading below, it shows S Flash OMAP3630
What am I doing wrong? Please help.
Thanks.

MK5.ESCORT said:
I have b
een trying for 3 days now to get a MB525 working. I have read hundreds of posts and followed tutorials with no luck
Please can someone help?
Phone powers on to animated moto blur logo, then repeats this 3 times but much faster. It then shows a t-mobile logo for about 15 seconds before going dark, then rebooting and looping.
I have tried wipe/reset from menu.
I have tried flashing 6 different sbf using RSD Lite v5.6 but flash files towards end with verifying checksum errors
RSD Lite doesnt display any details when i click show device, but under the 'model' heading below, it shows S Flash OMAP3630
What am I doing wrong? Please help.
Thanks.
Click to expand...
Click to collapse
Is your defy RED or GREEN? Try to flash correct SBF

If you wiped data from stock recovery after an sbf flash then you should not get boot loops. Try the ti omap blank flash option. If problem persists even after FULL sbf flash and above instructions then it looks to be a hardware issue
Sent from my MB526 using xda premium

Which sbf file did you flashed? Looks like you have a branded one. If you flashed the wrong sbf, it could cause this problem.
Sent from my HTC One X using xda premium

Please ask all questions in Q&A. Thread moved there.

First of all please find out what exact firmware you had before flash. Try to find exact same SBF from http://sbf.droid-developers.org/umts_jordan/list.php. If you moved up with roms then you can not go down any more as original SBF flashing will prevent it. Make sure you are flashing Defy and not Defy+ SBF's.
I experienced the same issue. My experience says that I could have bootloop from the same verions of ROM just for different region. In my case i was flashing 3.4.2 and although my phone was originally from blurred DACH then best result was always nonblur Nordic. Otherwise I ended ususally with bootloop.
Please answer all the questions below, so anyone who is willing to help can understand what exactly is going on:
* What region does your Defy belong to?
* Was it branded? What brand?
* Was it carrier locked?
* What firmware did you have before flashing?
* What SBF's you have been flashing without success?
* Did you have phone rooted before you did install SBF? If yes with what?
* Did you do factory/cache reset after SBF flashing?

Thanks guys (and gals?) for all your replies so far.
OK unfortunately I dont know the previous firmware etc. The phone was given to me by a friend who says they have never tried to flash/mod the phone (but that is unconfirmed)
All i know is that when I got the phone, it was stuck in a bootloop, part of which included a t-mobile splash screen.
SBF i have flashed unsucessfully are......
JRDNEM_U3_3.4.2_177003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_179002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_UCAJRDNFRYORTCOREEU_P023_A008_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_1796.1_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8TMGB03A.0R_PDS03C_USAJRDNFRYOTMGB_P023_A011_M003_HWp3_Service1FF.sbf
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
JRDNEM_U3_2.21.1_SIGNED_USAJRDNEMARAB1B8TMGB028.0R_USAJORDANTMGB_P030_A012_M001_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB02C.0R_USAJORDANRTGB_P035_A011_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Service1FF.sbf
Basically all t-mobile (uk) branded and uk unbranded roms.
All appear to flash ok, but then fail on verifying checksums.
I have not done factory/cache reset after flashing as the handsets is stuck in download/bootlader mode.
So do you think its case of keep on trying to flash various stock roms until i find one that it likes?
Thanks for all your help so far. Much appreciated
MK5

First try to get into stock recovery (check if possible): power it up while pressing volume down. If exclamation mark + triangle appear then press volume up and down simultaneously and choose wipe data/factory reset
BTW, you mentioned that when you got the phone it was in bootloop - was it somehow explained to you?

corrinti said:
First try to get into stock recovery (check if possible): power it up while pressing volume down. If exclamation mark + triangle appear then press volume up and down simultaneously and choose wipe data/factory reset
BTW, you mentioned that when you got the phone it was in bootloop - was it somehow explained to you?
Click to expand...
Click to collapse
I can get into stock recovery and do factory wipe/reset, but result is the same - bootloop
Should i keep trying different sbf's?
I dont want to kill the phone (obviously)

MK5.ESCORT said:
I can get into stock recovery and do factory wipe/reset, but result is the same - bootloop
Should i keep trying different sbf's?
I dont want to kill the phone (obviously)
Click to expand...
Click to collapse
Seems no other way, but it's not good that you don't know what BL your phone is and whether it's green or red lense.
Try BL5 in a first step - see the OP of this thread with links or try from this thread 'Common Problems/Questions' > Method 2

corrinti said:
Seems no other way, but it's not good that you don't know what BL your phone is and whether it's green or red lense.
Try BL5 in a first step - see the OP of this thread with links or try from this thread 'Common Problems/Questions' > Method 2
Click to expand...
Click to collapse
OK i just tried...
JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF
But it is the same result....
error verifying code group 32 checksums. File: 0x4805 Phone: 0xA8C7
plus others group 33 etc
Phone displays Bootloader 09.10
I think it is red lense
What should i try now?
I'm not 100% sure what your last post meant with regards to "Try BL5 in a first step" ?
Thanks

OK im about tearing my hair out with this phone.
Everything I try ends with same result - bootloop
Who would have thought flashing a phone could be so difficult?

Phone displays Bootloader 09.10
I think it is red lense
Click to expand...
Click to collapse
isn't this BL7 ?... so DFP231 Sbf ?
Sent from my MB526 using xda app-developers app

MK5.ESCORT said:
OK im about tearing my hair out with this phone.
Everything I try ends with same result - bootloop
Who would have thought flashing a phone could be so difficult?
Click to expand...
Click to collapse
It's difficult only when you do not know what is aboard - usually it's not difficult when you know its actual history.
But you didn't what what I proposed. You have flashed again BL4 sbf. Try BL5 or even BL6 (no way back to froyo) like Nordic Retail U3 4.5.1-134_DFP-137 from here
In my previous post I gave you some links to find out what is BLx
@cmadle
No, it doesn't mean it's BL7
Bootloader 09.10 is a standard one, also with Froyo BL4 ROMs

mb525 bayer
My Defy caught boot loop, sbf bl7 does not work. Recovery Motorola does not work, I can not do Wipe. PLEASE HELP

4igi4 said:
My Defy caught boot loop, sbf bl7 does not work. Recovery Motorola does not work, I can not do Wipe. PLEASE HELP
Click to expand...
Click to collapse
Try this thread
But also give there some more details how it happened

My defy suddenly turned off, when turning bootloop. Wgrywałem many SBF on this page but always bootloop i not did turned on stable recovery .I can't do Wipe

corrinti said:
It's difficult only when you do not know what is aboard - usually it's not difficult when you know its actual history.
But you didn't what what I proposed. You have flashed again BL4 sbf. Try BL5 or even BL6 (no way back to froyo) like Nordic Retail U3 4.5.1-134_DFP-137 from here
In my previous post I gave you some links to find out what is BLx
@cmadle
No, it doesn't mean it's BL7
Bootloader 09.10 is a standard one, also with Froyo BL4 ROMs
Click to expand...
Click to collapse
@4igi4 - I hope you get your phone fixed because I know how frustrating it is, but can you start your own thread please? Thanks
@corrinti - Thank You for all your help so far, its appreciated I flashed the file you suggested (Nordic Retail U3 4.5.1-134_DFP-137) but same result. I am a little confused, because the sbf you suggested is in list for defy plus? Isnt defy plus MB526? My phone is MB525. Or does this not matter?
Thanks
MK5

OK I tried 2 more sbf from linkk provided, but still error with verifying checksums
Retail British DFP-125 and DFP-237
Any more ideas please?
Thanks
Info from phone is:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1ac000170dc063010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: 512ac712004d25e05c275c482324c3ded11c6391
BP Public ID: 0000000000000000000000000000000000000000

MK5.ESCORT said:
OK I tried 2 more sbf from linkk provided, but still error with verifying checksums
Retail British DFP-125 and DFP-237
Any more ideas please?
Thanks
Info from phone is:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1ac000170dc063010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: 512ac712004d25e05c275c482324c3ded11c6391
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
Again, you didn't read the posts in links provided. If you really flashed DFP-237 then you are BL7 now. Anyway the phone is not screwed but just more work in rooting.
But was it flashed or you received an error during flash? (just hope so)
But there are many posts last days with the same problem - no sbf working and I have no idea how to overcome it. Sorry. Try to post in this thread
The only case I remember was some specific bootloader screen error + RSD error which indicated the hardware problem, (checksum of group 33 AFAIR)

[Q][Solved] Defy Red lense bricked, white LED on USB, showing in RSD Lite

Hi folks!
Could any of you awesome guys pls help me out?
My friend who also has a DEFY (Red Lense) foolishly flashed 2.1 sbf whereas he had already upgraded to 2.2.2 SEA.
As a result its soft bricked and does not power on.
When I connect it to the PC, I get only white notification LED on AND I get to show it up in RSDLite v5.3.1
It does not disappear either like I read was happening to some other folks with same problem.
So I went ahead and flashed the 2.2.2 SEA full sbf which I used to flash my DEFY and which worked flawlessly for my phone, BUT after a supposedly successful flash, RSDLite says rebooting but it does not turn on.
Instead it just goes back to white LED mode and is again visible in RSDLite
What are my options here?
Should I reflash 2.1 or is that a strict no - no?
Other info on the state of phone before being bricked: My friend was on Quarx JB 4.1.2 and decided to go back to Pikachu edition MIUI, but he did not format his system to ext3.
So obviously MIUI installation (which is via Aroma installer in Pikachu edition) failed.
Instead of flashing 2.2 sbf he flashed a 2.1 sbf and it worked according to what he told me, but the phone seemed real laggy and stuff. Then one day the phone just died and is in this state ever since.
Any and all help gladly appreciated!
Thanks in advance!

Update!
I talked to my friend and got the firmware he was trying to flash: Tmobile Defy Android 2.1
Although I can't find any such firmware here: http://forum.xda-developers.com/wiki/index.php?title=Motorola_Defy
Could anyone please help?

Just try out BL versions if these works. Go through BL4, BL5... and you will be successful with either. Yet DO NOT TRY OUT ONLY ONE BL!!!!!!!!
BTW I had the same problem, but mine was a second-hand Defy from a drunk man who tried to flash it Don't even ask about it xD

Solved!
Just flashed the CG v5 sbf and the nandroid backup and then the fixed sbf and was back on 2.2.2 nordic froyo!
http://forum.xda-developers.com/showthread.php?t=1216982
PS: Common Problems/Questions Method 1 for those who can't find in that long post.

[Q] Defy mb256 black screen white LED brick

So it started with rying to get the [Kitkat] CM11 Android 4.4 (I had the sbf from when I rooted the phone with this method: http://forum.xda-developers.com/showthread.php?p=31614617&nocache=1 ) but I needed the twrp recovery wich I tried to get but at the end couldn't and had to settle with 2ndInit Recovery but apparently it did't end up well because I bricked my phone without being able to acces boot, stock recovery and in the end running out of battery and using the Mcgyver thing wich worked. I tried a bunch of sbf's like:
- Android 2.3.5 Blur_Version.45.0.1250.MB526.NonEFIGSRetail.en.EU
- Android 2.3.6 Blur_Version.45.1.14.ME525+.ChinaRetail.en.CN
- Android 2.3.6 Blur_Version.45.0.2310.MB526.AsiaRetail.en.03
- Android 2.3.6 Blur_Version.45.0.2310.MB526.Retail.en.GB
- DFPRC_U_4.5.3-109_DPP-14-17_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P027_A024_HWp3a_Service1FF.sbf
- JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF
And none worked all go perfect till the end of the whole process en up getting PASS when rebooting and go back to the black screen. I'm kinda desparate because its a great phone and I'm afraid I broke it for good, by the way this is what i get in the RSD if it helps in anything:
RSD Lite v5.6
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 2c200215b9843b0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public
ID: ea4ef367c1b7077a82583145240414ae1fb81471
BP Public ID: 0000000000000000000000000000000000000000

kay.em said:
So it started with rying to get the [Kitkat] CM11 Android 4.4 (I had the sbf from when I rooted the phone with this method: http://forum.xda-developers.com/showthread.php?p=31614617&nocache=1 ) but I needed the twrp recovery wich I tried to get but at the end couldn't and had to settle with 2ndInit Recovery but apparently it did't end up well because I bricked my phone without being able to acces boot, stock recovery and in the end running out of battery and using the Mcgyver thing wich worked. I tried a bunch of sbf's like:
- Android 2.3.5 Blur_Version.45.0.1250.MB526.NonEFIGSRetail.en.EU
- Android 2.3.6 Blur_Version.45.1.14.ME525+.ChinaRetail.en.CN
- Android 2.3.6 Blur_Version.45.0.2310.MB526.AsiaRetail.en.03
- Android 2.3.6 Blur_Version.45.0.2310.MB526.Retail.en.GB
- DFPRC_U_4.5.3-109_DPP-14-17_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P027_A024_HWp3a_Service1FF.sbf
- JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF
And none worked all go perfect till the end of the whole process en up getting PASS when rebooting and go back to the black screen. I'm kinda desparate because its a great phone and I'm afraid I broke it for good, by the way this is what i get in the RSD if it helps in anything:
RSD Lite v5.6
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 2c200215b9843b0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public
ID: ea4ef367c1b7077a82583145240414ae1fb81471
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
Ok, it looks like the guide you followed was for BL7-phones. Though I don't know what version it had when bought, you made the mistake to flash Froyo stock roms AFTER flashing Gingerbread. That kind of downgrade is know to cause problems: section "CG Versions" "If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom."
So you need to flash a GB stock rom or try a downgrade guide: same link as above, section "Common Problems/Questions"

htto said:
Ok, it looks like the guide you followed was for BL7-phones. Though I don't know what version it had when bought, you made the mistake to flash Froyo stock roms AFTER flashing Gingerbread. That kind of downgrade is know to cause problems: section "CG Versions" "If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom."
So you need to flash a GB stock rom or try a downgrade guide: same link as above, section "Common Problems/Questions"
Click to expand...
Click to collapse
thanks for answering! I tired the guide you linked me but still It RDS gives me a PASS at the end of the whole thing and I'm back at the black screen I have no clue of what I can possibly do or if I left it useless. as for the version it had when I bought it I can't remember all of it (stupidly didn't make a backup or something) but it was one of the Taiwan ones Android 2.3.6
Blur_Version.45.0.1321.MB526.AsiaRetail.en.03 (not quite sure though)

kay.em said:
thanks for answering! I tired the guide you linked me but still It RDS gives me a PASS at the end of the whole thing and I'm back at the black screen I have no clue of what I can possibly do or if I left it useless. as for the version it had when I bought it I can't remember all of it (stupidly didn't make a backup or something) but it was one of the Taiwan ones Android 2.3.6
Blur_Version.45.0.1321.MB526.AsiaRetail.en.03 (not quite sure though)
Click to expand...
Click to collapse
Well if it originally was GingerBread-based, then you have to stick with GB-SBFs, probably even a BL7. The problem is probably, that one/some of the ROMs you flashed might have altered either partition layout or some non-standard data on one of the partitions. I don't know if there actually is an SBF that writes all partitions or at least /system /cache and /data. That could probably help, since you're unable to wipe/factory reset those partitions.
At least your defy is still flashable, so the bootloader seems to be ok. Does RSDlite produce some kind of log? Maybe it writes some checksum warning? Personally I use sbf_flash for linux, which checks checksums, flashes and even verifies the flashed data.
Umm, what about this thread, post #4:
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.

htto said:
Well if it originally was GingerBread-based, then you have to stick with GB-SBFs, probably even a BL7. The problem is probably, that one/some of the ROMs you flashed might have altered either partition layout or some non-standard data on one of the partitions. I don't know if there actually is an SBF that writes all partitions or at least /system /cache and /data. That could probably help, since you're unable to wipe/factory reset those partitions.
At least your defy is still flashable, so the bootloader seems to be ok. Does RSDlite produce some kind of log? Maybe it writes some checksum warning? Personally I use sbf_flash for linux, which checks checksums, flashes and even verifies the flashed data.
Umm, what about this thread, post #4:
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
It's Alive!! Thaks! you're awsome I really appreciate taking the time to help me :good: cheers