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 ????
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
cute_kayani said:
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
Click to expand...
Click to collapse
I think I got the answer for you......
Use below mentioned steps and share the outcome:
1. Download the compressed SBF and extract using any software like 7zip or something - http://www.mediafire.com/?s3uc8cb782w1oue
[Note: Do not use any download manager while downloading.]
2. Use RSD Lite to flash the phone with the SBF file;
3. After flashing let the phone boot up and hopefully it will resolve the issue.
However if the phone is still in boot loops then try entering Stock recovery and wipe data/format and wipe cache also.
Please use the above steps and share the outcome.
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
pranks1989 said:
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
Click to expand...
Click to collapse
I understand your concern and I appreciate your comment however, I would like to point this out that this firmware is for "India, Indonesia, Malaysia, Philippines, Thailand, Vietnam" and its safe to flash I have flashed it multiple times and its Rootable and even my flash is healthy.
You may visit this link and Control+F "JRDNEM_U3_3.4.3-33-1":
http://and-developers.com/sbf:defy
The chinese firmware which is suspicious of burning flash is "China - JDGC_U6_0.26.0" [Correct me if I'm wrong.]
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
cute_kayani said:
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
Click to expand...
Click to collapse
You may use this firmware or any different firmware from this link : http://and-developers.com/sbf:defy
The ROM which I have given you link is Rootable however not down-gradable.
You may refer this extract from All-in-one-Guide-for-Defy
SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.6, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
ATTENTION: This CG 7 Version is NOT rooteable. You wont be able to flash a lower version ROM nor Root to use CWM.
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
Official SBFs
Here is a list of all the OFFICIAL SBFs, meaning they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
Ref == http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
The only thing which is important here will be to use a Froyo or newer version SBF.
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani said:
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
Click to expand...
Click to collapse
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani I think you double posted mistakenly....
Have already answered your query above
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Click to expand...
Click to collapse
---------- Post added at 09:26 PM ---------- Previous post was at 09:12 PM ----------
One important thing for your information is the reason behind those black screens was that you must have flashed Froyo SBF before; which was not down-gradable and now at this point you were trying Éclair which resulted in this issue.
So, the Downgradibility of your previous flashed SBF was causing this issue.
Now, as you have flashed this Froyo SBF; so, now onward in case you need to flash you phone you need to use SBF which should be Froyo or newer and must have “3.4.3” or later Build Numbers.
Hope this helps someone who needs this information.
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
cute_kayani said:
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
Click to expand...
Click to collapse
LOL its official Froyo it might have more bugs
haha okay i am moving to miui.... but from past 7 days my defy remains dead due to Miui weekly rom update
hopefully this time miui wont make any problem
LOL
All the very best this time ..
You know what last week I also updated to MIUI 2.3.23 and my wifi was not working with that ROM however, it was working fine with my CM9 as I had dual boot.
Please update me if you also face this issue with the MIUI 2.3.30
currently am on 2.3.23 every thing is okay, and wifi also working now am updating it to 2.3.30. will tell you if there any wifi bug.
Will wait for your review!!
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
cute_kayani said:
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
Click to expand...
Click to collapse
Lol 2GB internal memory occupied
Yesterday night I flashed with MotoGinger III for a change... so far so good. However, AutoWifi fix is resetting my wifi pwd every 15 mins or so ..
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
Hi,today I have flashed original Motorola .sbf ,I downloaded it from here. It is 3.4.2_179-002, Retail Central Europe version. Now,after flashing it with RSD Lite the phone does not boot. There is no even Motorola logo at the start,nothing,its dead. How can I start the phone with this original .sbf? I want to have original froyo on the phone,and I know how to get back to CM10 but im not interesting in that now.
Thanks.
markos807 said:
Hi,today I have flashed original Motorola .sbf ,I downloaded it . . .... I know how to get back to CM10 but im not interesting in that now.
Thanks.
Click to expand...
Click to collapse
markos807, did the SBF flashing process complete successfully and did u get the message "Please manually reboot phone" in RDSLite window?
Did u verify the MD5sum of the downloaded SBF against the MD5sum given in the download page to check if the downloaded SBF file is not corrupted?
Are u still able to go to the Bootloader by pressing VOL UP+POWER button when the phone is switched off?
Only if u provide the above information, I can suggest what can be done next.
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
markos807 said:
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
Click to expand...
Click to collapse
Might I suggest, pull your Defy battery, replace it, do not attempt to get into bootloader, Leave it off. Just plug it in with usb after booting up RSD lite and see if connects on it's own. Sounds like a bad flash. I've connected that way numerous times.
markos807 said:
1.I dont remember what was the message,but I think it wasnt "Please manually reboot phone",but it was done,some other message saying its done
2.How to do that?
3.I cannot go into bootloader and when I connect a phone via usb to the PC the RSD Lite recognizes it so I can flash some other verified sbf.
Thanks for trying
Click to expand...
Click to collapse
1. Even I dont remember the exact message But I remember that it asks us to reboot the phone manually.
2. If the SBF which u are using is corrupted while downloading, it may lead to bad flash. U can google and download and use any of the md5sum checking tools. I use winmd5 application(I'm using Windows in my laptop), which is easy to use and it has UI unlike some other md5sum tools which have to be run through command line.
3. If RSD Lite recognizes ur phone, then try flashing the SBF once again. But ensure that the SBF is not corrupted as mentioned in point 2. If ur SBF is corrupted, try downloading it again. There are chances for a file to get corrupted while downloading. That is the reason why md5sum is mentioned in the download page to verify the file after download.
Winmd5 app says "Matched!". That means it is good?
Yes, if the MD5sum matches it means that the SBF file is not corrupted. U try flashing the same SBF again and see if it works.
@ markos807: Were u able to flash SBF successfully? I would like to know if ur defy is working fine now
Gingerbread (BL7) back to Froyo?
Did you already flash a Defy+ ROM with Gingerbread?
From a BL7 ROM there is no way back to Froyo. BL7 doesn't support that.
When I wanted to go back to froyo, I was flashing this sbf: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
And that broke my flashlight! And because of that I want to go back to other official froyo sbf to see will the flashlight work. Do you know any other fix for the flashlight? Anything please?
Also, I am flashing same sbf second time now, will post the results.
Edit: Cannot boot the phone with any .sbf downloaded from here. The only .sbf that I can flash and boot the phone is JDGC_U6_2.13.0 China Unicom and that one broke my flashlight.
markos807 said:
When I wanted to go back to froyo, I was flashing this sbf: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
And that broke my flashlight! And because of that I want to go back to other official froyo sbf to see will the flashlight work. Do you know any other fix for the flashlight? Anything please?
Also, I am flashing same sbf second time now, will post the results.
Edit: Cannot boot the phone with any .sbf downloaded from here. The only .sbf that I can flash and boot the phone is JDGC_U6_2.13.0 China Unicom and that one broke my flashlight.
Click to expand...
Click to collapse
Mate, as you flashed BL6 sbf then you are stuck with BL6 and no way back to froyo other than chinese one.
Your flashlight could be burnt out - in such a case only moto service can help
What do you mean you cannot boot with any sbf from walter79 thread? Have you tried all of them? (You shouldn't). Or only froyo ones?
If you tried only froyos, then you can flash gingerbread BL6 to check your flashlight
And have you tried wiping data and cache from stock recovery? Is it accessible with power + volume down?
No, I cannot acess stock recovery. I have tried only froyo ones. Can you give me the link for that BL6 GB, I`ll flash it tomorrow because I really want to fix my flashlight.
markos807 said:
No, I cannot acess stock recovery. I have tried only froyo ones. Can you give me the link for that BL6 GB, I`ll flash it tomorrow because I really want to fix my flashlight.
Click to expand...
Click to collapse
Try any from a range 4.5.1-134_DFP-125 up to DFP-161. Higher are usually BL7, lower are BL5, so no use to flash
Link to the sbfs
I have succesfully boot up a phone with this sbf: DEFYPLUS_U3_4.5.1-134_DFP-125_GR_SIGN.. but my flashlight is still not working. The camera is not working at all.
markos807 said:
I have succesfully boot up a phone with this sbf: DEFYPLUS_U3_4.5.1-134_DFP-125_GR_SIGN.. but my flashlight is still not working. The camera is not working at all.
Click to expand...
Click to collapse
Well, I suppose you've burnt your flash unfortunately with chinese froyo.
Your camera will not work with GB ROMS. It's normal. but it was you who flashed BL6 ROM on your green defy
You have to go to CM10 2ndboot builds to have your camera working again.
For flash I suppoose only moto service can help
Hi folks
I've bricked my Defy and trying to get it back on line with RSD lite (5.6). I've tried the following SBF from sbf.droid-developers.org/umts_jordan however it seems to be corrupt as RSD complains about not enough disk spare which is not true. When I open the gz file winzip cannot determine the file size.
JRDNEM_U3_3.4.2_145-012_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B5TEL03B.0R_PDS03C_USAJRDNFRYOTELSTRA_P013_A007_M003_HWp3_Service1FF.sbf.gz
I downloaded an earlier version and RSD can work with it fine but as it's old than my current BL it doesn't run and just get the usual black screen.
Does anyone know where I can get a "Good" version of this (or a later one) please.
Okay I've moved on and managed to upload a Telstra 3.4.2 SBF by shorting the file name.
My next problem is that the device is in a boot loop. If I try to power on with sound - I get the little andriod logo with an exclamation mark so it doesn't go into a recovery menu.
Once again, anyone know how to get throught this?
Cheers
tastech said:
Okay I've moved on and managed to upload a Telstra 3.4.2 SBF by shorting the file name.
My next problem is that the device is in a boot loop. If I try to power on with sound - I get the little andriod logo with an exclamation mark so it doesn't go into a recovery menu.
Once again, anyone know how to get throught this?
Cheers
Click to expand...
Click to collapse
Its all about flashing the correct SBF....but first tell me do you want to run the stock ROM or are you planning to run a custom one..
Anyway...may be this will help you....
http://forum.xda-developers.com/showthread.php?t=1825064
If it does not...then let me know further problems you are facing...
Thanks
Thanks for your replay. Yes it is all up to the correct sbf but neither the Telstra ones worked.
I did however have CM7/2ndInit installed before and reading around that was the problem when trying to get the phone back stock. You learn as you go I guess.
Finally got it up and running using forum.xda-developers.com/showthread.php?t=1152377
Question is from this can I get back to CM7 etc from here?
Yep I can! All up and running again with CM7.
Thanks