[Q] Can't delete anything on my internal memory! - Milestone 2 General

Hello! I'm a proud owner of a Milestone 2 (I don't know if this goes to Droid 2 or Droid 2 Global ) and I have a quite big problem:
My phone was running very bad, a lot of FC and slowness so I decided to wipe, so I did, went to recovery, wipe data, wipe cache, all done perfectly.
Reset the phone and what happened? Everything was exactly the same as before, I tried to deleted applications and when I restart the phone they appear all again and random resets.
I went mad and installed a .SBF with RSDLite, it completed and failed at checksum group errors and bricks my phone to "CRITICAL ERROR: DE A1" screen.
I revived my phone by installing the .SBF through booteable Ubuntu, but it's ALL the SAME as before.
I would love all the help you could give me and sorry for my bad english.
Greetings.
EDIT: I'm really sorry! I didn't know there was a Milestone 2 section.

did you get it fixed?
if not, which sbf did you use?

sd_shadow said:
did you get it fixed?
if not, which sbf did you use?
Click to expand...
Click to collapse
Nope yet. I used the SBF Flashing in Linux with Ubuntu Live CD with the Brazil GingerBread sbf for Milestone 2 (also tried UK)
If I try to flash with RSD Lite won't pass the CHECKSUM ERRORs and bricks my phone to CRITICAL DEA1, with Ubuntu won't pass checksums without errors but it boots.
Thanks for the reply.

what does bootloader say

sd_shadow said:
what does bootloader say
Click to expand...
Click to collapse
CODE CORRUPT if I'm not mistaken.

which bootloader do you have?

sd_shadow said:
which bootloader do you have?
Click to expand...
Click to collapse
Bootloader 70.12
Thank you for the reply.

are you verifying md5 checksums?
getting sbfs from
http://sbf.droid-developers.org/umts_milestone2/list.php

sd_shadow said:
are you verifying [...] md5 checksums? [/URL]
getting sbfs from [...]
Click to expand...
Click to collapse
I did the check method and none of the codes matched, which SBF should I download now?
Thanks for the reply!

doesn't matter if the checksums don't match, the file is not getting downloaded correct
pick one and keep trying
or try a different pc or internet source

sd_shadow said:
doesn't matter if the checksums don't match, the file is not getting downloaded correct
pick one and keep trying
or try a different pc or internet source
Click to expand...
Click to collapse
The checksums matched (I was checking the .sbf decompressed when I should checking the compressed one), but nothing, tried 2-3 sbfs (slow internet, downloading them takes forever) and the same as before, if done through RSDLite Bootloader with Code Corrupt and if done through Ubuntu all is same as before.
Thank you for the fast reply.

have installed Moto Drivers 5.4.0 or better
RSD Lite 5.7
moto usb data cable,
different 2.0 usb port sometimes back usb ports work better than front
different pc

sd_shadow said:
have installed Moto Drivers 5.4.0 or better
RSD Lite 5.7
moto usb data cable,
different 2.0 usb port sometimes back usb ports work better than front
different pc
Click to expand...
Click to collapse
I was using RSD Lite 6.1, should I downgrade?

should be fine, but I haven't used higher than 5.7
but when it's not working, try something different

sd_shadow said:
should be fine, but I haven't used higher than 5.7
but when it's not working, try something different
Click to expand...
Click to collapse
Nope, done with back USBs, a few SBFs, RSD Lite 5.7 and nope, Critical Error DEA1.
Hopefully, still can flash through Ubuntu and revive it.
I don't really know what else I can try, thanks a lot for the replies tho!
Merry Christmas.

Related

Need help.. Bootloader Err:A5,70,70,00,1F

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.

[Q] RSD Lite not recognizing Droid X

I am stuck on the BootLoader screen after installing the 2.3.340 update.zip.
I'm trying to flash the 2.3.320 sbf file using RSD Lite but it isn't recognizing my phone. I reinstalled the drivers and restarted my machine.
RSD Lite shows a device connect to USB Port 1
But it says :
Model - S Flash OMAP3630 MI
IMEI/ESN/MEID - N/A
When I try to flash the sbf file I get a Status of 'Failed Flashing Process, Unable to retrieve initialization values from INI file (0x7029); phone connected
What version of RSD?
mob87 said:
What version of RSD?
Click to expand...
Click to collapse
Version 4.6
You need 4.8 or above
mob87 said:
You need 4.8 or above
Click to expand...
Click to collapse
Downloaded version 4.9. Will test it out and let you know.
tgadd said:
Downloaded version 4.9. Will test it out and let you know.
Click to expand...
Click to collapse
Still not working. Going to go to Verizon and sweeten up with a rep. Thanks for the help.
Do you have the Droid X drivers installed? Did you run as administrator?
mob87 said:
Do you have the Droid X drivers installed? Did you run as administrator?
Click to expand...
Click to collapse
Yes and yes.
My battery ran out last night so I'm having a co-worker charge it up for me. I'm going to try one last time when I get off work today and then head over to Verizon.
im having a simiar issue but rsd lite 4.8 wont even recognize my device and i sweaer ive got the drivers but im unable to find them or a guide to make sure i even installed them correctly, could i get pointed to where they are please
Download the driver from here, not the charging one but the other one, unzip and install.
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
mob87 said:
Download the driver from here, not the charging one but the other one, unzip and install.
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
Click to expand...
Click to collapse
That is what I've installed and still no luck.
I think it's working. All looks to be in good order. Flashing at the moment
tgadd said:
I think it's working. All looks to be in good order. Flashing at the moment
Click to expand...
Click to collapse
I found out that error 0x7029 usually related that the .sbf file is not in the C:\ root folder. So I moved it there.
Then I couldn't hit "start" after selecting the .sbf file because "start" was greyed out. I found a post here explaining how to fix it.
Follow his steps completely and it'll solve this problem.
Give RSD a little time to see your phone too. The first time I ran it, I had to wait about a minute until it populated, now it comes right up. I had a terrible time getting it to work though... Just keep tryin'!

[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...

[Need help]

guys i flashed to gb2.3.4. It went smooth. But due to the bugs i wanted to go back to 1.8.3. so i tried to flash back using 1.5.7(because i have this built full) but while flashing it failed. now if i want to go back to 2.3.4 again it wont start and writes modem start failed on startup red moto screen.please guys guide me.
amrutpritam said:
guys i flashed to gb2.3.4. It went smooth. But due to the bugs i wanted to go back to 1.8.3. so i tried to flash back using 1.5.7(because i have this built full) but while flashing it failed. now if i want to go back to 2.3.4 again it wont start and writes modem start failed on startup red moto screen.please guys guide me.
Click to expand...
Click to collapse
Did you unlock the bootloader again? Afaik, it relocks the bootloader once you do sbf flash.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
I'm pretty sure the bootloader can't relock. Unlocking physically blows a fuse.
Sent from my MAtrix
amrutpritam said:
guys i flashed to gb2.3.4. It went smooth. But due to the bugs i wanted to go back to 1.8.3. so i tried to flash back using 1.5.7(because i have this built full) but while flashing it failed. now if i want to go back to 2.3.4 again it wont start and writes modem start failed on startup red moto screen.please guys guide me.
Click to expand...
Click to collapse
Download 1.87 and try to flash that.
JayRolla said:
Download 1.87 and try to flash that.
Click to expand...
Click to collapse
is there a new version 1.87?
is there any other link to download the full version of 1.8.3?The m3 superthread gives mega upload links and i am unable to download it from that site
thanks in advance
ceo.mtcl said:
Did you unlock the bootloader again? Afaik, it relocks the bootloader once you do sbf flash.
Click to expand...
Click to collapse
At this time you CANT RELOCK the bootloader. Flashing another SBF only removes the "Unlocked" at the top left. But the phone is still unlocked.
amrutpritam said:
is there any other link to download the full version of 1.8.3?The m3 superthread gives mega upload links and i am unable to download it from that site
thanks in advance
Click to expand...
Click to collapse
They have both megaupload and filesonic.
http://forum.xda-developers.com/showthread.php?t=1125944
oops i missed the filesonic link.recently i noticed my phone always fails to flash at the point where STARTING BP INTERFACE is written in rsd lite progress coloumn.after that if i try to start the phone it says modem failed to start(0) starting rsd lite protocol. Is it a hard brick? I had read in this forum somewhere that hard brick is possible after boot loader unlock. i like this phone very much. so worrying so much.
amrutpritam said:
oops i missed the filesonic link.recently i noticed my phone always fails to flash at the point where STARTING BP INTERFACE is written in rsd lite progress coloumn.after that if i try to start the phone it says modem failed to start(0) starting rsd lite protocol. Is it a hard brick? I had read in this forum somewhere that hard brick is possible after boot loader unlock. i like this phone very much. so worrying so much.
Click to expand...
Click to collapse
I would redownload the SBF. And try again. Try a new USB Cable. Try a diffirent USB Port. And leave the computer alone while it running.
donniesd said:
I would redownload the SBF. And try again. Try a new USB Cable. Try a diffirent USB Port. And leave the computer alone while it running.
Click to expand...
Click to collapse
Thanks i will definitely do that
Gitbrew has all the files you need.
Sent from my MB860 using XDA Premium App
no success
i redownloaded the firmware
used another usb cable
another usb port(this time the back of pc)
but it again failed in switching device to BP pass through mode.Pc actually searches for a driver for QHSUSB_DLOAD and doesnot find it. then fails to switch the device
i tried by formatting my computer and doing it again but without success.
please guys help me

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"?

Categories

Resources