[Q] What can be done to recover from the MBM-flash mode? (Defy XT) - Defy Q&A, Help & Troubleshooting

Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
The problem is that, I couldn't find a tested (official/unofficial) ClockworkMod recovery for use with Defy XT. I could do with installing some Chinese release of ICS for Defy XT (SBF), but, I wanted to try CM10; it appeared more fascinating. So, anyway, I thought I could use Koushik's custom recovery build script on his website (builder.clockworkmod.com). So, I did the process of obtaining the stock "recovery.img", plugging it in that script, and obtained a new custom-built CWM. The real problem which I am not able to come out of is now - After flashing it, on the next reboot, it is going into the "MBM-flash mode", and it throws out an "error 0301", and doesn't go further than that. In this mode, I gathered that it will be able to communicate to a computer (RSD lite) over USB, and so, I installed it and was able to detect the device, but I'm not able to find out, what to do next to get it back to normal working condition.
Since that error screen I see now is basically a flashing tool, I was thinking, reflashing the recovery partition with the stock "recovery.img" (have a back up) should solve the problem. But, I'm not able to find out how to do it...
If there is anyone else who has faced a similar problem and found a solution, it would be really good of you to share it. Or, if there is anyone who knows how to work with RSD lite, could you suggest a method to flash the "recovery" section only through this software? (I'm guessing an XML file should be enough, but I don't know how to write it; format).
Hopefully I'll get speedy replies .

QuaziRandom said:
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse

I tried...
Srika said:
QuaziRandom said:
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse

QuaziRandom said:
Srika said:
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse

Srika said:
QuaziRandom said:
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
any other way to backup my stock rom b4 flashing the new ics rom?
Click to expand...
Click to collapse

Please ask all questions in the Q&A section. Thread moved there.

Related

[Q] Backing-up and flashing

Hey, guys (and girls? )! Just got a new DEFY+ couple of days back and I'd like to get the most out of it. It's already working all smooth and sexy, but I'm sure it can do better. So I need some assistance
Phone info:
DEFY+ (MB526)
Android 2.3.4
System 45.0.74.MB526.Retail.en.DE
Kernel 2.6.32.9-gbad50c3
Build 4.5.1-134_DFP-74
I've rooted it yesterday and I'm pretty sure it was successful, since the phone is working and I've got SuperUser on it since then (I've followed the root part of the all-in-one super DEFY guide thread)
About backing up, I would like to be able to go back to my old backup at any time. Is that even possible? I know I probably never will go back to it, but I like to play things safe. If it is possible, could you teach me how or point me to some nice guide/thread on that?
When it comes to flashing, I'd like to try CM, WAJKIUI and MS2G. Any more ROMs that are a must try? Now, I didn't quite understand... Are there different versions for defy and defy+? Or...which ROMs are compatible with defy+? I've read somewhere that all defy ROMs can't use defy+'s battery properly, so that's what concerns me. Nandload? How to?
I'm sorry if these are stupid questions, I've tried finding out everything from the guides, but I just didn't find enough information... I do have RSD (v5.0.0, is it okay?) and the drivers, all set up. I'm not asking for anyone to write an essay for me, it will be perfectly fine if you just point me to some (really really) good guides. I'll be grateful for any and every answer!
*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?
I can beg if need be
"*EDIT #1* Well, I've tried to learn some more... Let's go step by step. Should I install 2ndInit app or some other custom recovery app?"
Hi,
as I've seen the guides, yes.
I've defy, so I didn't try it, but heard from many people with defy+ with CM or MIUI.
BUT before it I suggest to you:
- get a stock sbf of your rom. It is necessary if you want get back the original factory state. hope here you find it: http://forum.xda-developers.com/showthread.php?t=966537
- install titanium backup from market (I know this, but you can install any similar app) and make a full backup (all user and system app). It saves all data, installed apps with settings ...
- make backup of your contacts and sms-s with stock app (it is possible I think)
- make backup of your sd content
After that you can install 2ndinitdefy. Follow the instructions in the program. I suggest 1.4.2 version. If it doesn't work go to 2.0. The 2.0 has instructions not on the main screen but in its menu.
After the 2 reboot (regarding 2ndinit install) you can do a nandroid backup with clockworkmod recovery.
Reboot, push vol down at blue led (after start with 8-10 sec). You are at bootloader. Use vol up/down to navigate and power to enter a menu. Go to recovery-> custom recovery->backup and recovery->backup all. It takes some time. You can save this nandroid to computer (just for safety ) You find it in sd/clockworkmod/backup.
Now you have backups. Go ahead, install the custom rom of your choice.
I recommend WajkIUI. You find the link in my signature and you find installing instructions in Wajk's first post. And of course there are defy+ users in that thread as I remember, you can ask question there.
ps: everything is your responsibility
Was it helpful? Just use thank button
Good luck bro/sis !!!
Thank you for such a long reply!
I have installed 2ndInit, using the v2.0 installer, but I chose the stable version of the 2nd init itself, instead of the latest one. That stable one said it was meant for CM and MIUI, so I'm guessing I'll be alright with WajkIUI as well!
I'll follow the steps you gave me for making a complete backup of everything on my phone and then I'll start looking for a ROM that's fully mb526 compatible (I need >10 posts to be able to post in the development section :/ )
P.S. I'm a bro
I see. This 10 post rule a bit annoying. But as I know you can send private message to anyone. In the Wajkiui thread there are some people with 526.
I've got my 10 posts Thank you once more and I'm sure we'll be talking again soon!
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
niksy+ said:
I'm having a hard time finding a full SBF of my stock ROM...
It's 4.5.1-134_DFP-74 (Android 2.3.4)
I don't really understand the codes in that name, so can someone please tell me if I could flash some close to this sbf if I ever need to? I've found some with just that value after "...DFP-" different. Would they be okay?
Please let me know! I wanna load up something different, but don't want to do so until I have a full sbf as well, just in case of emergency
Click to expand...
Click to collapse
You should ask Walter79. I found similar sbf as yours in his thread /forum.xda-developers.com/showthread.php?t=966537/ at "my roms" link:
www.4shared.com/folder/YpyTOtp4/Defy-roms.html
Bests
Mate, thanks for the info, but I've already found and flashed a full .sbf The topic said it was 2.3.4, while it turned out to be 2.3.5, but I don't mind, got my phone working again after a failed flashing of cm7.2..!
Cheers

[Q] Defy near death or worse. Please help!

Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2

[Q] Defy MB525 - Cant install Any rom without bricking the phone.

Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??
Spersico said:
Hi to you all.
I'll tell you my problem:
As the title express, i can't install any rom.
I had problems with calls with the CM10.2 in my phone, so i tried to put some other rom. I put the mokee os 43.
It worked, but the WiFi didn't. So i tried again, with other rom. I've got bootlop.
Then i've full flashed the phone (you know.. with the RSD lite) with a sbf from where i live (JORLA_U3_3.4.2_108-5_SIGNED (a rom from Argentina, with Personal Carrier)). The phone worked, but when i installed the Custom rom (CM10.1 i think) i had no-signal with my phone (installed and tried everything to manage the baseband issue). Tried another rom, bootloop again.
Well, long story short:
Now, i cant install any SBF from Argentina of the MB525, just an USA version of it, because otherwise it bricks my phone (no bootloop, just black screen, recognisable by RSD).
I can install, though, the Defy+ version of those roms, but each time that i try to flash it to a cm7, cm10,cm10.2 rom, my phone bricks again. Showing me an error( "Err:A5,70,00,00,23" and prompting to put the usb cable and start over),and getting stuck in the debug mode (the part where you install the sbf), and can't get through that,
As you can tell, i've got serious trouble. I would love to start from scratch, but my phone is getting rebelious.
I've read in other forums, searching for the error above, and supossedly now my phone is no longer a defy, but a defy+, and i should install sbf's of THAT phone, but i've done it, and i still get the error each time i flash (superclick, 2ndinit,reboot, wipedata/cache/dalvik, cm7, gapps).
What should i do?.
Right now i'm in
DFL_U3_4.5.2_51-50_SIGNED_USADEFYB25RETLALA007.0R_STABLE45LADEFYRETLA_P008_A014_M001_HWp3_Service1FF.sbf
wainting for instructions. I'm tired already of blindly trying new sbf with no results. What do i do??
Click to expand...
Click to collapse
Try the retail Taiwanese DFP-231.
Thanks!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
Thanks dude, i've made that, but i still have problems, it helped me a lot though, since that in a moment not even one rom of the defy plus worked, except this one.
I keep dealing with the issue, but using this guide, i think i might get to the point that i want (that is... everything except the stock rom).
http://forum.xda-developers.com/showthread.php?t=1889325
Thanks!
I made it!
hotdog125 said:
Try the retail Taiwanese DFP-231.
Click to expand...
Click to collapse
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.
Spersico said:
I made it. After using the guide linked before, i put cm10 in the phone, and worked.
I would've liked to install CM7, but at the moment, i've lost like 20/30 hs in making my phone work.
Right now, i just want to enjoy it!
After my problem with the roms. i had problems rooting the phone, 'cause the rooting method i used didn't worked anymore (superoneclick). I had to use the double-flash-method(from the link on top). After that, i installed 2ndInit and everything worked allright. Except CM7. I couldnt find a CM7 that didn't brick my phone. So... i'm stuck with CM10 (for now).. until 4.3 reach a certain level of maturity.
The problem is Solved - If Any Moderator sees this, can close the thread.
Click to expand...
Click to collapse
You can use framaroot instead of using the double flash method. See the new CM7.2 by maniac in the dev thread. Try it.

[Q] Stuck. Anybody have T-mo Froyo SBF and/or advice?

Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.

[Q] Recovery problems on Defy+ while updating to CM11

Hey!
I had CM10.2 on my Defy+, and tried to just follow Quarx simple post:
http://forum.xda-developers.com/showthread.php?t=2515036
I had some trouble with the update recovery (bad zip), reformatted my SD with sdcard.org's official formatting tool, and it worked.
The Quarx website seems to be down, so I downloaded the CM11 rom with the most recent date from http://defy.bytekiste.de/cm11-nightly-defy+/
Which is where I got the update-recovery as well, so I figured that would be fine.
Got a status 7 error (this package is for "MB526" but your device is ""), so I tried fiddling with the verification, editing the rom script (those few lines you have to delete), according to various topics on the status 7 subject. Nothing worked.
People in treads advice different recovery files, so I manually flashed TWRP from here:
http://teamw.in/project/twrp2/91
I rebooted into recovery again, an it just gives a blank (but lit) screen. I can still access the bootmenu, but not recovery, so I guess TWRP doesn't work with my phone. Should have read the comments on that downloadpage I guess... So I went on to find this "goomanager" people are talking about but all I get are dead links, so I tried the ROMManager and TWRPManager apps, but I can't find any reference to Defy+, Jordan or MB526 within those apps when they ask you to select a device.
I'm not an expert, so I was like, lets start all over from scratch to get recovery working again. Any recovery, I don't care. So I went back to:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which is what I used for when I bought the phone to get root, bootmenu & recovery through ADB from the windows command line.
I'm trying to follow that to at least recover the ICS recovery which I had, but I'm stuck there as well. When I switch USB from mass storage mode to "tools only", ADB disconnects, and when I leave it in mass storage mode, well, the sdcard is not mounted to the phone so I can't use ADB on it.
Can anyone give me a push in the right direction? Can I restore the update-recovery from Quarx CM11 thread somehow?
So I got adb to function (how, I do not know), ran the stuff here:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which gives me Bootmenu 0.6.1 (I had Bootmenu 2.0.0 before?). And it doesn't include a functional recovery, or a functional 2ndinit, so I completely (soft)bricked my phone now :laugh: Both recovery & boot give errors about missing sh scripts.
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
okdewit said:
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
Click to expand...
Click to collapse
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files -- yes, you have to go through several pages to get there and then you have to select the specific sbf that you want, but it's there (here for Defy: http://sbf.droid-developers.org/phone.php?device=27 or here for Defy+: http://sbf.droid-developers.org/phone.php?device=28).
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
JimboN said:
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files
Click to expand...
Click to collapse
Yesterday when I tried it, the whole droid-developers website just gave an Nginx server error, but I'm glad to see it's up again. Gonna load up RSDLite now and give it one last try!
JimboN said:
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
Click to expand...
Click to collapse
I fully realize that, it's mostly frustration with myself and a series of bad actions which led me to lock up my phone further and further with each action. I realized the risk in advance, so luckily I do have a full backup and a backup phone, but it still hurts a bit to see your beloved device dying on the operating table because of your own stupidity.
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
okdewit said:
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
Click to expand...
Click to collapse
Glad to hear you were successful.
Yep, know the frustration of my own stupid actions screwing up my phone and when you go to fix it, that don't work right either -- been there & done that.
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
I've found one BIG culprit in my previous methodology: copying files through motorola phone portal is just plain wrong. I kept getting "bad zip" and other verification errors. Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well. I've also used the windows program Teracopy (for CRC checks) instead of the built-in windows explorer file copier. :good:
Thanks a lot for the support, if you had not pointed out that the SBF filehost was working fine again, this nice phone would've been thrown away.
okdewit said:
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
Click to expand...
Click to collapse
Fantastic! CM11 works better for me than any other rom that i've tried (certainly smoother and probably faster), still has a few bugs but so did all the others. Best of all it's the latest android and can run all the latest apps.
okdewit said:
Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
Click to expand...
Click to collapse
Hmm... That's interesting. I've used USB Mass Storage to do just what you attempted to do without a problem -- good to know as a potential issue.
okdewit said:
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well.
Click to expand...
Click to collapse
Thanks for the tip.

Categories

Resources