Database Users

[Q] RSD Lite - Failing

Hey guys,
During installing some ROM on my defy , it got messed up...
I used RSD lite to flash my defy completely , but It'll execute till 100% then there will be some error in " verifying checksums" and later it just FAILS.
I've tried the following
*flashing different ROMS (ard 10)
* using the latest RSD (5.6)
*charging my battery completely
*storing the sbf in C:
* using the RSD lite in admin mode
*also sometimes it does not even create that "flash error log"
I really dunno guys/.... please help... is my defy bricked??

You have installed a rom of your country? Where it was made the phone?

I'm pretty sure RSD Lite is for flashing SBF files, not ROMs.

@defy_jay
Which SBF have you flashed?
Try to flash SBFs from http://sbf.droid-developers.org/umts_jordan/list.php.
If you have a defy+ use this link:
http://sbf.droid-developers.org/umts_jordanplus/list.php
Is your cable eventually weak?
Have you made a Factoryreset before flashing with RSD-Lite?
Have you renamed the SBF in short name, like ABC.SBF?

trying now...
@ RATTAR
Which SBF have you flashed?
**-- i'm flashing all kinds of sbf online but eventually gets stuck at 100 % ..
Try to flash SBFs from (some url)
If you have a defy+ use this link:
**-- I have a defy but it's updatd to a 2.6.9 kernel.. so i'm trying SBFs from both the links you've pasted
Is your cable eventually weak?
**-- i doubt the cable is weak cause its reading when i connect and its also flashing till the 100 %
Have you made a Factoryreset before flashing with RSD-Lite?
Have you renamed the SBF in short name, like ABC.SBF?
**-- yeah tried the short name thing...

..
@Glaux
sorry that was a mistake..i'm flashing SBFs only...
@kroix10
does it matter which country's sbf you install ??
i'm installing what ever i get.. but it's an Indian make so i'm flashing "Retail Asia" or should i flash anything specific ??

Bricked Defy - Working only Bootloader after fail flash (error veryfying code group)

Hi
I had to flash my Motorola Defy to Official 2.2.2 Froyo Android, but during flashing appeared - error veryfying Code Group 32 checksum
I had 2.1 android before so I dunno why this error appeared.
I tried install another sbf's, usb drivers, install from another usb cabel and PC.
Everytime I got this same error.
I even tried install those sbf's from Linux CD (Knopixx) but this didnt work too.
If u have any idea's please help ;<
Ps. sorry for my poor english.

shockwave7 said:
Hi
I had to flash my Motorola Defy to Official 2.2.2 Froyo Android, but during flashing appeared - error veryfying Code Group 32 checksum
I had 2.1 android before so I dunno why this error appeared.
I tried install another sbf's, usb drivers, install from another usb cabel and PC.
Everytime I got this same error.
I even tried install those sbf's from Linux CD (Knopixx) but this didnt work too.
If u have any idea's please help ;<
Ps. sorry for my poor english.
Click to expand...
Click to collapse
Maybe the sbf's got damaged during download. Or the sbf's itself are broken. Try to redownload or use other sbf's.
Don't worry, as long as the bootloader's still working, your phone is most likely not yet bricked

Happen to me today so here is the sbf that I used:
http://www.mediafire.com/?vbcv0lhopulntx8
after that I installed 2nd and CMW and flashed CM9+++

yodawg said:
Maybe the sbf's got damaged during download. Or the sbf's itself are broken. Try to redownload or use other sbf's.
Don't worry, as long as the bootloader's still working, your phone is most likely not yet bricked
Click to expand...
Click to collapse
I downloaded maybe 5 same sbf and still this error appear.
Downloaded 15 another sbf's and nothing worked ;/
x-Moi-x said:
Happen to me today so here is the sbf that I used:
after that I installed 2nd and CMW and flashed CM9+++
Click to expand...
Click to collapse
I tried flash this sbf but again same Error veryfying code group 32 checksum...

Are you using the latest version of RSD Lite again(I did it with v5.6) and the latest version of the drivers.

x-Moi-x said:
Are you using the latest version of RSD Lite again(I did it with v5.6) and the latest version of the drivers.
Click to expand...
Click to collapse
I'm using RSD Lite 5.7 and new drivers and this file didn't want to flash ;/
Anyone have any other idea? ;/

Can anyone help me?
I'm losing hope ;/

shockwave7 said:
Can anyone help me?
I'm losing hope ;/
Click to expand...
Click to collapse
Do you still have warranty? Red or Green Lens? Any modifications made?
I could only repeat: Search for different sbf's and try them. Maybe reflash the kernel before that if it doesn't work.

yodawg said:
Do you still have warranty? Red or Green Lens? Any modifications made?
I could only repeat: Search for different sbf's and try them. Maybe reflash the kernel before that if it doesn't work.
Click to expand...
Click to collapse
Have red lens and I still have warranty.
I tried with so many sbf and any wont to work.
What do u mean: reflash kernel?

shockwave7 said:
Have red lens and I still have warranty.
I tried with so many sbf and any wont to work.
What do u mean: reflash kernel?
Click to expand...
Click to collapse
Hmm if you only did "official things" like trying to flash official firmware without any modifications then why not claim your warranty and send your phone to customer service?

@shockwave
Have you tried, to shorten the name of the sbf-file, in ABC.SBF.
Also you should put the shorten SBF in the program directory of rsdlite.
It sounds to me, that the string of the SBF is too long, so rsdlite creates errors while depacking the sbf for flashing.

yodawg said:
Hmm if you only did "official things" like trying to flash official firmware without any modifications then why not claim your warranty and send your phone to customer service?
Click to expand...
Click to collapse
I think I will do do that, but I wanted do it faster. On warranty I need to wait many time ;/

Do you flashed a defy plus sbf? I think that you upgrade your BL to 6 or 7. That's why when you put froyo it doesn't start

jmms94 said:
Do you flashed a defy plus sbf? I think that you upgrade your BL to 6 or 7. That's why when you put froyo it doesn't start
Click to expand...
Click to collapse
Nope, I will find some defy+ sbf I try to flash it.

shockwave7 said:
Nope, I will find some defy+ sbf I try to flash it.
Click to expand...
Click to collapse
I think you misunderstood jmms94. I think he thought you had already flashed a Defy+ build accidentially and that this would be the cause for your error!

yodawg said:
I think you misunderstood jmms94. I think he thought you had already flashed a Defy+ build accidentially and that this would be the cause for your error!
Click to expand...
Click to collapse
I tried install 2.2.2 Froyo for normal Defy not Defy+ at first time. I dont have any idea what i cant do more. I will try reinstall my RDS Lite and Drivers, again...

RATTAR said:
@shockwave
Have you tried, to shorten the name of the sbf-file, in ABC.SBF.
Also you should put the shorten SBF in the program directory of rsdlite.
It sounds to me, that the string of the SBF is too long, so rsdlite creates errors while depacking the sbf for flashing.
Click to expand...
Click to collapse
Have you already tried this??

yodawg said:
Have you already tried this??
Click to expand...
Click to collapse
Yep, same error... ;(

Did you repeat after trying hard reset?
Sent from my MB525 using xda app-developers app

Shafirul said:
Did you repeat after trying hard reset?
Click to expand...
Click to collapse
What is a "hard reset"?

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] defy stuck on bootloder :/

hi, i try to flash my defy but the rsd all the time failed and he always get to the bootloader and i can't get to the recovery.
and i don't have the "M" logo, i try to flash the nordic sbf,
i am sure thet the sbf work fine becuse i flashed it befor.
i add a photo of the rsd progress.
if someone know how to solve thet error i was happy .
please help me! thank you.
srv1.jpg.co.il/9/50f336fd13ec3.jpg

dowloand the european rom 2.2.2 sbf and after flash this mayby wiil work and make sure you are on bl3

nikolas60 said:
dowloand the european rom 2.2.2 sbf and after flash this mayby wiil work and make sure you are on bl3
Click to expand...
Click to collapse
i download the european rom and try to flash it and i get the same error .
i noticed thet when the progress get status "phone[0000]: Code Group 32 checksums match." is stuck for 2 min and then he Change to status "Phone[0000]: Error verifying Code Group 33 checksums. file 0x8BAC, Phone: 0x4805"
the Code Group 33 and above get error verifying
.
srv1.jpg.co.il/2/50f3e8b81b771.jpg

omri9180 said:
i download the european rom and try to flash it and i get the same error .
i noticed thet when the progress get status "phone[0000]: Code Group 32 checksums match." is stuck for 2 min and then he Change to status "Phone[0000]: Error verifying Code Group 33 checksums. file 0x8BAC, Phone: 0x4805"
the Code Group 33 and above get error verifying
.
srv1.jpg.co.il/2/50f3e8b81b771.jpg
Click to expand...
Click to collapse
Search your USB cable for possible damage because if data error appear during flashing process you obtain error at checksums.

pgreed said:
Search your USB cable for possible damage because if data error appear during flashing process you obtain error at checksums.
Click to expand...
Click to collapse
i try to use another cabel and computer and all the time is the same error I'm starting to to give up on him:crying:

omri9180 said:
i download the european rom and try to flash it and i get the same error .
i noticed thet when the progress get status "phone[0000]: Code Group 32 checksums match." is stuck for 2 min and then he Change to status "Phone[0000]: Error verifying Code Group 33 checksums. file 0x8BAC, Phone: 0x4805"
the Code Group 33 and above get error verifying
.
srv1.jpg.co.il/2/50f3e8b81b771.jpg
Click to expand...
Click to collapse
i had the same problem months ago.try with another sbf.if doesnt work,you have to get it back to service as the flash memory got broken

Cristi_10 said:
i had the same problem months ago.try with another sbf.if doesnt work,you have to get it back to service as the flash memory got broken
Click to expand...
Click to collapse
if you can give me a sbf file that you think that work i was happy, but i think you right that my flash memory got broken .:crying:

omri9180 said:
if you can give me a sbf file that you think that work i was happy, but i think you right that my flash memory got broken .:crying:
Click to expand...
Click to collapse
Try central european (or nordic) 3.43 sbf and is better if you make a checksum of the sbf after downloading

MB526 Slim-mb526-4.4.2.build.3-UNOFFICIAL-20140215-2305 DEAD for no reason?! HELP

On its Defy installed the following files listed below. One day, for unknown reasons, the phone turned off , after restarting all the settings were gone , I decided to install the latest Slim- mb526 - 4.4.2.build.3.85 - UNOFFICIAL - 20140323 -0023 but encountered a problem with the wipe . I decided to use it again DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF but have failed to complete the installation. I have also tried other SBF but nothing helps . Please advice , the phone after inserting the battery shows a message Code Corrupt , Battery ok
PLEASE HELP ANYONE
I can not find any solution on the web, already sifted through forums and websites . I'm afraid I can not help yourself in saving my phone without your help . Please interest. I will answer any of your questions , I really like this phone , I do not want to lose him !
I'm using the latest rsd lite 6.1.6 . The phone is unlocked. I no longer have warranty.
Files installed on your phone:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF
Slim- mb526 - 4.4.2.build.3 - UNOFFICIAL - 20140215 - 2305
minimal_Slim_AIO_gapps.4.4.2.build.3
Framaroot - 1.9.1
SndInitDefy_2.3
defy_twrp_recovery_2.6.3.0

If you get code corrupt with dfp 231, then it unfortunately would imply eMMC issues, because it cannot happen in theory. Although i have never seen anyone fix this error, you can try with the ti blank flash option enabled
Sent from my MB526 using Tapatalk

Is RSD recognizing your phone?

Yes RSD show my phone and flashing then give me replay "error verifying code group 33 checksums...."
Where I can find the ti blank flash option?

keny1992 said:
Yes RSD show my phone and flashing then give me replay "error verifying code group 33 checksums...."
Where I can find the ti blank flash option?
Click to expand...
Click to collapse
Try stock 231 sbf without root included.

Can You give me full name of this rom? I don't want to get a mistake...

Anyone else have some ideas?

keny1992 said:
Anyone else have some ideas?
Click to expand...
Click to collapse
I don't think anything else can be done. You can still try different SBFs from - http://sbf.droid-developers.org/phone.php?device=28 (try retail Taiwanese).