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...
Related
I need help.. I failed trying to sbf my phone and now i see a black screen with this message every time i turn on my phone.
Bootloader
D2.35
Err:A5,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB
What do i do??
anducly said:
I need help.. I failed trying to sbf my phone and now i see a black screen with this message every time i turn on my phone.
Bootloader
D2.35
Err:A5,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB
What do i do??
Click to expand...
Click to collapse
What phone D2 or D2 G and which SBF did you use?
I assume you used the 2.2.00 sbf when you needed the 2.3.20 SBF once you have the 2.3.20 update the bootloader is changed and won't accept the 2.2.0 sbf.
IF that's the case you need to try flashing it with the 2.3.20 SBF found HERE
Read the bottom of THIS post if you get a bootloop or stuck at the M logo screen.
it works!! Thank you so much!!
anducly said:
it works!! Thank you so much!!
Click to expand...
Click to collapse
Glad it worked but what specifically worked? I gave a bunch of information, I just want to know which pieces helped in your case.
THANK YOU SOOOOOOOOO MUCH!!!!! I know that this post is a little old but I thought that my phone was finished. Again Thank You!
Thank you sooooooo much!!!! I thought all hope was lost.
Had this problem the other night but all is good now
Sent from my Motorola Droid 2 with Fission 2.3.1
This worked to fix my phone, thx so much
i used the 2.3.20 SBF
will this work on the droid x?
myrakle said:
will this work on the droid x?
Click to expand...
Click to collapse
You probably flashed the wrong SBF. You need to find the latest DX SBF they should be found in the DX section of XDA. Off the top of my head I can't think of the latest release.
Sent from my DROID2 using XDA App
anducly said:
I need help.. I failed trying to sbf my phone and now i see a black screen with this message every time i turn on my phone.
Bootloader
D2.35
Err:A5,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB
What do i do??
Click to expand...
Click to collapse
I have a similar problem. I just got this phone and dont know the history other than the ESN is clear with vzw. It goes str8 to the BL screen and has this...
Bootloader
D2.35
Battery OK
OK to program
Tranfer Mode: USB
I Dloaded RSD lite 4.7 an the 2.35 BL sbf as well as the orig 2.2 and 2.3 FW sbf's. RSD will communicate with the phone. I can reload the BL sbf if I open the sbf file but none of the FW sbf will load in RSD, the start button command stays grayed out. Also in RSD on line 1 of the phone status it shows connected but above that in the device properties box info for the meid/esn etc show N/A.
I can access the recovery menu and at the bottom there is an error report for accessing recovery cache in a folder path.
Can I put an update.zip on an sd card and try to revive this thing that way or maybe I am doing something wrong? I am guessing this is the result of some botched flash job.
I have done some modding on my Droid X such as backing it up, deodexing and put the Liberty ROM on it as well and changing ROMS on my android tablet so I have some of the basics down but after much searching & reading I am seeking help with this one. Thanks in advance!
Edit: Now my battery is dead, I have found in other threads that a blank software device wont charge the battery if this helps
Ronbo85 said:
I have a similar problem. I just got this phone and dont know the history other than the ESN is clear with vzw.
I Dloaded RSD lite 4.7 an the 2.35 BL sbf as well as the orig 2.2 and 2.3 FW sbf's. RSD will communicate with the phone. I can reload the BL sbf if I open the sbf file but none of the FW sbf will load in RSD.
Click to expand...
Click to collapse
Maybe try flashing in linux and make sure you have read up about flashing SBF's on a DX. I don't know which one to flash as this is the D2 section and I have a D2.
I can access the recovery menu and at the bottom there is an error report for accessing recovery cache in a folder path.
Click to expand...
Click to collapse
This error is normal disregard it.
Can I put an update.zip on an sd card and try to revive this thing that way or maybe I am doing something wrong? I am guessing this is the result of some botched flash job.
Click to expand...
Click to collapse
That would work if you can find an update.zip made by moto that will go through the bootloader. And it doesn't really matter how it got here but probably it is a bad flash or a wrong ROM. (You might try connecting it via wall charger (not USB) while it's powered down then turn it on and see if you can get into clockwork recovery.)
Edit: Now my battery is dead, I have found in other threads that a blank software device wont charge the battery if this helps
Click to expand...
Click to collapse
You need to find someone with a DX to swap/charge your battery with so you can get in and flash it or you need an external battery charger (one that will charge the battery outside of the phone).
Sent from my DROID2 using XDA App
Hi, thank you for the reply. I know I made comments about my DX I have as well but to be clear this is a Droid 2 I am working on. I will get the battery charged somehow and let you know what I come up with, thanks again
Ronbo85 said:
Hi, thank you for the reply. I know I made comments about my DX I have as well but to be clear this is a Droid 2 I am working on.
Click to expand...
Click to collapse
Oh. In that case you need the 2.3.20 SBF found here http://droid2files.com/tools/VRZ_A955_2.3.20_1FF_01.sbf after you can get the phone charged. (If it helps the D2 has the same size battery as the D1 so you can swap/charge a D2 battery with a D2 or a D1.)
Also try finding RSDLite 4.8 or 4.9 as they might work better for you. I'd give you a link but I Haven't flashed an SBF with RSDlite I just use linux.
Sent from my DROID2 using XDA App
Cool thank you again. I got the battery charging via a rig I have done before with other devices from a camera charger. My linux(zorin) machine lost keyboard function out of the clear blue I havent had a chance to sort it yet(another project lol) but I do have a live usb thumb drive setup to use for linux. I'll try on this windows machine for now.
I'll keep you posted as to the results
well I got the battery charged up. I still have this problem when I select either the 2.2 or 2.3 sbf files the start button for applying the flash stays grayed out as if the files are invalid. If I select a bootloader sbf the start button is ok and I can load the BL sbf. I tried switching to rsd 4.8 too. I will keep playing around with it and maybe try to get my linux pc going.
Ok well even tho I had a few copies of the sbf files I went ahead and dloaded the one you linked. It would load in the rsd app but when I hit start to apply I get.... "Failed Flashing Process (0x7100) and this happens right away
Ronbo85 said:
Ok well even tho I had a few copies of the sbf files I went ahead and dloaded the one you linked. It would load in the rsd app but when I hit start to apply I get.... "Failed Flashing Process (0x7100) and this happens right away
Click to expand...
Click to collapse
Are you still using rsdlite 4.7? I had problems with it not too long ago. Downloaded 4.8 and worked like a charm. Hope you get it sorted out.
Sent from my ultra fast Liberated Droid 2
Ronbo85 said:
Ok well even tho I had a few copies of the sbf files I went ahead and dloaded the one you linked. It would load in the rsd app but when I hit start to apply I get.... "Failed Flashing Process (0x7100) and this happens right away
Click to expand...
Click to collapse
You might need to put the file in the C: drive of your windows box. At least that's what a another forum post found from a Google search suggested.
Or try linux Check here for more info: http://forum.xda-developers.com/showthread.php?t=804088. It's an old version of Ubuntu and there are somethings I want to add to it, I'll be updating it as soon as I have some free time to put it together using the 10.10 version.
I found this link... http://androidforums.com/droid-all-...-failed-flashing-process-0x7100-rsd-lite.html check out post #32
It does make a difference where the file is located yes and I got the sbf to perform the flash but after a lengthy process looks like about 3 steps and it takes 3-5 min I end up with a fail messege. There is more info I could provide but its been a long Monday I need to give it a break and now the batt is low again.
Thank you all again for your much appreciated help. I will regroup tomorrow. I will try to log in on my phone to see any ideas I mite need to think over.
Hey i will try to be as precise as possible. I'm posting in this section because in the general section the help isn't as effective as here.
Here is my problem:
A few days ago i flashed GB MIUI on my Milestone 2 everything worked perfectly and i used the phone a whole day. That night i've put the phone to charge and went to bed. Il the morning when i push the power button the phone didn't boot. I was stuck at the first M bootscreen (Red at the time).
I wasn't able to do anything no recovery the phone didn't seem to be charging so i decided to flash Stock FR SBF (One i used many times)
Once completed i let the phone tying to Boot for about one hour. After that i pulled the battery out and tried to get to recovery but no success. Holding the X button while booting wasn't getting me to recovery because the wouldn't get pass the First Moto bootscreen (Recovery open after that).
So i've flashed since then a handful of SBF from and-developpers:
2.2 FR
2.2 CH
2.2 UK
2.2.2 FR
2.2.2 CH
2.2.2 UK
2.2.2 Hong Kong
2.2 China
Official GB Leak signed
Still wasn't able to get throught the first moto bootscreen.
r2beta0 had an idea so if someone can please help me get through this. I think i'm done with flashing things...
r2beta0 said:
Hmm, I just had an idea that needs elaboration. As we know we can flash any partition of the phone using sbf_flash or RSD Lite. If his problem really can be solved doing a data wipe it would be also solved by flashing a new "empty" CG37.smg. It doesn't need to be signed because /data is not checked by bootloader. So, we need a Milestone2 /data empty image (CG37.smg). One could do a data wipe and take the image of with dd command, but it would be a HUGE file (6,5 GB). I don't know if we can use a smaller file just to clean his /data. Maybe someone can elaborate that.
Click to expand...
Click to collapse
dangpzanco said:
Maybe you can flash a modded SBF, with a modded CG37 and a new CG that points to addresses from the middle of data to its end, and make two partitions with data spare space for the dual booting project, is that even possible?
Well, at least when you pack and zip it the SBF won't be hard to upload.
PS: Does the Milestone 1 full SBFs have the data CG included?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
I tried holding X button while i plug the phone the Wall charger but no sucess either. I just can't get to the screen with the Exclamation point...
I've tried to be as precise as possible to help people who will or already tried to help me. Please don't delete my thread or move it after i've put so much effort in this...
I've search in hundreads of threads around different forum XDA is my last chance...
I thanks everyone who will take some time to help me or even at least read this.
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I just did it no results still the same!
I don't think it looks good.
I didn't pull out the battery yet i wan't to give it a chance. I'll edit this post
Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.
Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)
r2beta0 said:
Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.
Click to expand...
Click to collapse
Emacore said:
Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)
Click to expand...
Click to collapse
I removed the sim card removed the sdcard, charge the battery with a milestone 1 avec two different charger. No results
@r2beta0 i think you are right i'll wait i someone help me until tomorrow evening if not i'll send it back to moto.
Have you tried to use sbf_flash on linux/mac?
Sent from my Milestone 2 XDA App
I think i'm going to try that. Will report later
r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I have the same probleme .... And this don't work for me too.....
Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !
EVEALEX62 said:
I have the same probleme .... And this don't work for me too.....
Click to expand...
Click to collapse
I've tried Linux but no result... We are 3 french who have the exact same probleme it can't be Hardware?
Our Milestone 2 are somewhat different than others... I've phoned motorola for my problem today they told me to send it to a partner repair center but he warned me that if they discover i did something to the phone it will cost my a lot of money...
I'm sending it monday morning i'm really hoping for a solution before than...
Im not sure about service sbf vs the one that wipes user data. We have that kind of sbf for m2?
On the other side, looks like ROM chip go bad.
I'll ask some obvious question...you did not have any errors when flashing ? it always complete the process? Can you get into the bootloader when it print version 70.12 or 70.13 ?
Another obvious thing, did you verify md5 after downloading sbf ?
pat972 said:
Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !
Click to expand...
Click to collapse
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................
EVEALEX62 said:
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................
Click to expand...
Click to collapse
So it happenned both to us when we intalled MIUI so the problem is MIUI. Because i was using CM7 since Endless7 post the instruction avec Defy's ROM. And the phone was perfect...
We both have French Milestone 2 and i don't think it is my fault. I quite shure i did everything straight. I maybe a noob in dev or other things. But I have experience in flashing things...
My bootloader is 70.12 so it's different than Alex. And i used just like Alex the French Stock sbf i used everything i needed a freash clean install
When i flash i get to the "Please reboot phone manually" like everytime and then pull the battery go to bootloader and get finish
I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone
Motodoido said:
I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone
Click to expand...
Click to collapse
My phone is supposed to have the 70.12 bootloader right? If i flash the new one won't the repair center see that i modified the software?
The is no 70.12 bootloader on and-developper so how do i get back?
My phone doesn't not get to PASS it never did even in past... Except when i could do a wipe data and cache before flash
If you flash the 70.13 you do not be able to back to 70.12, so think before. When RSD is in reboot your phone 30%, I always remove my phone and never have problems
If you want try, here is the 70.13
The bootloader for the sbf 2.2.2 is 70.13 ! I remenber well, i did the official update on a windows pc, and it started by updating bootloader! But it's good news and may be just some sort of sbf incompatibility with the bootloader...just find the correct ones?
Sent from my MotoA953 using XDA App
pat972 said:
But it's good news
Click to expand...
Click to collapse
What is the good news ????
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"?
Soo, woke up this morning and noticed that the phone was stucked. I mean, could do anything to it, so I just took battery off and then put it back. I got this M logo then when I got to this circles flashing around it, screen just got black. Looked on the web, saw I can try a factory reset settings. Did that and after phone just restarted when it got again to circles flashing, phone just restarted. Didn't wanted to go any further. So I tried to reflash it (battery was at ~ 80%), i keep getting this errors in RSD Lite : Error veryfing Code group XX checksums. Almost same errors all the time. There is something to be done ?
Thank you in advance !
Phone MB526, Android version 2.3.6.
Carrier : Vodafone Romania, but i think is Central Europe retail software version (Tried that too, same errors).
Nebeleizis said:
Soo, woke up this morning and noticed that the phone was stucked. I mean, could do anything to it, so I just took battery off and then put it back. I got this M logo then when I got to this circles flashing around it, screen just got black. Looked on the web, saw I can try a factory reset settings. Did that and after phone just restarted when it got again to circles flashing, phone just restarted. Didn't wanted to go any further. So I tried to reflash it (battery was at ~ 80%), i keep getting this errors in RSD Lite : Error veryfing Code group XX checksums. Almost same errors all the time. There is something to be done ?
Thank you in advance !
Phone MB526, Android version 2.3.6.
Carrier : Vodafone Romania, but i think is Central Europe retail software version (Tried that too, same errors).
Click to expand...
Click to collapse
I think you got an incomplete download.
All of them ? Cause I tried 7 SBF files till now. I don't know what should I do more ...
Nebeleizis said:
All of them ? Cause I tried 7 SBF files till now. I don't know what should I do more ...
Click to expand...
Click to collapse
Maybe try opening RSDLite with administrator privileges. Are you sure you are flashing only Defy+ SBFs?
hotdog125 said:
Maybe try opening RSDLite with administrator privileges. Are you sure you are flashing only Defy+ SBFs?
Click to expand...
Click to collapse
I opened RSDLite with admin. And yes, only defy+. Now my battery is dead and I'm trying to revive it with usb cable cutted. I'll try more and see if I can make my phone work again ...
Nebeleizis said:
I opened RSDLite with admin. And yes, only defy+. Now my battery is dead and I'm trying to revive it with usb cable cutted. I'll try more and see if I can make my phone work again ...
Click to expand...
Click to collapse
Try this - http://www.droidxforums.com/forum/droid-x-rooted-issues/20588-sbf-problems-help-9.html#post230970
Hello,
My phone was stuck in a boot so I've tried to flash it by using a SBF file. Even though this was successful, when the phone reboots, I get a bootloader 09.10 error: A5,69,35,00,27 ?!
The phone doesn't go pass that so I'm not sure what else to try ?!
Many thanks in advance
kokolino23 said:
Hello,
My phone was stuck in a boot so I've tried to flash it by using a SBF file. Even though this was successful, when the phone reboots, I get a bootloader 09.10 error: A5,69,35,00,27 ?!
The phone doesn't go pass that so I'm not sure what else to try ?!
Many thanks in advance
Click to expand...
Click to collapse
I had the same problem several weeks ago -- got the same error message (not sure about the exact numbers but very similar). I couldn't even get to the stock recovery. I tried several different sbfs until it finally worked. The Nordic sbf is what finally worked for me. I don't know if it was the Nordic sbf that 'fixed' it or the multiple attempts.
What rom were you previously using? I had been on CM11 - Nov nightly. Others have had trouble with going back to stock after being on the CM11 New Life ROM. In another case that I'm aware of, they flashed the same sbf several time before it finally worked.
JimboN said:
I had the same problem several weeks ago -- got the same error message (not sure about the exact numbers but very similar). I couldn't even get to the stock recovery. I tried several different sbfs until it finally worked. The Nordic sbf is what finally worked for me. I don't know if it was the Nordic sbf that 'fixed' it or the multiple attempts.
What rom were you previously using? I had been on CM11 - Nov nightly. Others have had trouble with going back to stock after being on the CM11 New Life ROM. In another case that I'm aware of, they flashed the same sbf several time before it finally worked.
Click to expand...
Click to collapse
Can I ask where did you got that sbf from, please?
My phone is not even recognised by the laptop now :crying:
Also looks like it's not charging either ?!