Related
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...
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 ????
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)
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
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
pikaetas said:
Hi everybody.
Being short; I had miui 2.3.7f, I decided to change to the new miui V5, but the installation was wrong.
I couldn´t make the Wipes properly because the unit E:\ was unmounted, and the result, a slow system.
I decided to change the rom, but in this case,not using the TWRP recovery. I decoided to flashing SBF files via RSD.
The first one,was interrupt by slow battery, I tried later and nothing happens.
Reading in the forum, some user recommended this one DEFYPLUS_U3_4.5.1-134_DFP-2312_TMOUK_SIGN_DE..
and actually, is the only rom that I tried, that it shows the "M" logo before bootloader
At this point the bootloader 09.10 shows me the ERR:a5,69,35,00,27
I´m not sure but, could be a problem of kernel ? For put a rom of defy+?
I perfectly know, there are 4 or 5 threads about that, I read, but wasn´t useful for me
everything is welcome !!!
Click to expand...
Click to collapse
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Zeroemd said:
re-flash sbf when RSDlite says that the device is rebooting and it does not, remove the battery and put it in again and go to stock recovery (vol down + power,when the android with the ! appear press both volume buttons) and make a factory reset.
Click to expand...
Click to collapse
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
pikaetas said:
Thanks zeromd,I tried but when Im trying PWR+VOLDOWN, nothing happens.
Only when I stop to press, the bootloader apears again, with the error .
Could you explain me why the defyplus rom seems to boot, and not the rest ?
Click to expand...
Click to collapse
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Zeroemd said:
I own a Green Lens defy (mb525).
Yet I searched a bit and a guy in snother forum solved this problem flashing
but as the name suggests it is intended for the Defy+ (mb526) but It seems that you have flashed one alredy, so idk if you want to try it. and if by any chance the .sbf is not on you main HDD put it on you desktop.
Click to expand...
Click to collapse
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
pikaetas said:
Thanks again, but the file is´corrupt
Ill try to find it and I´ll let you know.
Click to expand...
Click to collapse
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
pikaetas said:
Hi again.
Zeroemd, I´ve got some news........ IT´S ALIVE !!!!!!:laugh::laugh::laugh:
I finally found the correct SBF, it´s that
vvvvv.mediafire.com/download/31pbi59a275f7ry/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Now I want to go step by step making things as better as possible since arrive to Kit Kat !!!
The first .. nandroid.
Thanks a lot
Click to expand...
Click to collapse
Well I am Glad your phone is alive !
anything you need PM me :good: