Hi Everyone,
I am trying to load a rooted SBF file onto my Motorola Defy+ (MB526). Basically I had some issues with installing CM10, and decided to revert back to CM9, however I received some Encryption Unsuccessful messages. The specific message that I received lead me down the track of flashing SBFs to the phone (as per the link above). My challenge is that if I use the rooted SBF provided then the phone keeps returning to the Bootloader window which displays Err:A5,69,35,00,27!
The only SBF that will restore my phone back to healthy operation is the DEFYPLUS_U3_4.5.1-134_DFP-231_AU_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P021_A030_Service1FF.sbf.gz, which is the retail version for Australian's like myself! There doesn't seem to be any rooted version for Australian phones.
If anybody can suggest a rooted SBF that will work with an Australian MB526 (originally from the Telstra network) it will be greatly appreciated.
Kind Regards,
David
Howdy mate, i just flash this on my mates simlocked telstra defy+
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
it booted fine and rooted. didnt have to wipe and format either. may have to google sbf.
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf Not working
Hello Whatrom,
Thanks for your input. Unfortunately I have not been as fortunate as you. Previously I have flashed this ROM, and my situation did not improve. However it has been a few weeks since my first attempt(s), so I decided to try again today. Whilst the ROM flash appears to work fine, with "Finish" clearly displayed in the RSD Lite Program (on Windows), the Motorola Defy still shows error data on it's screen.
Here is what I see on the Motorola Defy's screen -
Bootloader
09.10
Err:A5,69,35,00,27
Click to expand...
Click to collapse
If you have any further recommendations please let me know.
Kind Regards,
Davo
That's not possible. Are you sure you are flashing dfp231 sbf? It's bootloader version 7(max known), so it cannot give you the boot loader error
Sent from my MB526 using Tapatalk 2
Definitely using the stated SBF, and definitely have version 9 of the boot loader!
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo
Mr Davo said:
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo
Click to expand...
Click to collapse
No, you cannot downgrade bootloader:laugh:.
Mr Davo said:
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo
Click to expand...
Click to collapse
The version which appears at the boot loader screen does not correspond to the actual bl version(surprisingly). So that 9 which you're referring to is not the boot loader version. The sbf you're using has the highest possible such version(7), which implies that no one should face this issue while trying to flash this sbf, because the device cannot have a version higher than the one in this sbf(7).
It's possible that due to eMMC failure, the sbf is never flashed properly, and so the boot loader error occurs
That's only my guess though
Also, sorry but boot loader version can only be upgraded, not downgraded. You can't upgrade since you're at the maximum value already.
But if your phone works with a specific sbf, flash it and root using framaroot(search on Google). It is an android application which can be simply installed and run to root the phone. Then try to fix your network using baseband switcher.
Sent from my MB526 using Tapatalk 2
I have just had to do this today.
I followed the steps provided here http://forum.xda-developers.com/showthread.php?t=1542956 (use the first SBF for each step) and the phone appears to be working fine and http://forum.xda-developers.com/showthread.php?p=12837303 installed fine.
About to try some custom ROMs now to see if this what this little phone can handle
Related
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.
I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
ive tried to install the Argen2Stone 2.7RE on my milestone 2 UK retail running on stock GB 2.3.4!
the funny thing is it always end up on black screen after i restore the argen2stone nandroid and applying the FixedSBF before rebooting my MS2.. i cant access the recovery because after the red motorola logo its already black screen.
Did i do something wrong about it? in the thread of Argen2Stone it say its for any ROM so assuming it should work on UK GB stock!.. Hope anyone can help thanks!
Edit: Got it working using the fixed SBF provided by endless7 CM7.. the thing is the FixedSBF.zip provided in argen2stone is not compatible with UK GB 2.3.4 so after i installed the argen2stone 2.7RE, reboot and gone on a black screen then flashed the fixedSBF using RSD lite then recovery, factory reset..
try entering motorola recovery by holding x when powering on. If it will let you get that far, do factory reset from there an see how that goes. Also make sure you are trying to flash the right sbf, because even group users have to flash a fixed sbf. So you didn't recesarily flash the right one just cause you flashed one
I cant be screwed to find the direct link now as I‘m on my tablet, so please refer to my guide here: http://forum.xda-developers.com/showthread.php?t=1464507
Around halfway down you will find a section titled install instructions (gingerbread users). There I have the correct link for the fixed sbf you need (this one needs to be flashed with rsd lite btw)
Edit: now that I think about it, your mistake was flashing the fixed sbf. All it does is chanew your kernel, and you were already on the one you needed. So flashing the sbf changed it to a kernel no longer compatible with your phone since you updated to 2.3.6 (non downgradable).
Flashing the sbf I'm referring to earlier should fix you up
DreadPirateDan said:
try entering motorola recovery by holding x when powering on. If it will let you get that far, do factory reset from there an see how that goes. Also make sure you are trying to flash the right sbf, because even group users have to flash a fixed sbf. So you didn't recesarily flash the right one just cause you flashed one
I cant be screwed to find the direct link now as I‘m on my tablet, so please refer to my guide here: http://forum.xda-developers.com/showthread.php?t=1464507
Around halfway down you will find a section titled install instructions (gingerbread users). There I have the correct link for the fixed sbf you need (this one needs to be flashed with rsd lite btw)
Edit: now that I think about it, your mistake was flashing the fixed sbf. All it does is chanew your kernel, and you were already on the one you needed. So flashing the sbf changed it to a kernel no longer compatible with your phone since you updated to 2.3.6 (non downgradable).
Flashing the sbf I'm referring to earlier should fix you up
Click to expand...
Click to collapse
thanks for the reply.. well even the stock recovery is not accessible the option i did was reflash all over again.. thankfully i got it working using fixedSBF from endless7 CM7.
Edit: revert back to stock GB rom.. this rom eats up too much RAM >.<...
in stock rom i can manage a 220mb free ram on standby but this rom when on standby for too long manage 175-185mb free rom.. maybe ill try CM9 next!
hi guys, someone could use the FMRadio??
americogiovani said:
hi guys, someone could use the FMRadio??
Click to expand...
Click to collapse
Unfortunately, it's not possible to use the FM radio in our Milestone 2, no matter with which app and rom.
got an error while flashing atrix 2.3.4 stock to 2.3.6 using RSD lite, can anyone help me getting out of this? will be much appericiated tnx in advance
error is:
failed to boot 4
starting rsd mode
soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.
gnahc79 said:
soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.
Click to expand...
Click to collapse
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
sunny1119 said:
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
Click to expand...
Click to collapse
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.
TravisAntonio said:
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.
Click to expand...
Click to collapse
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!
DJHile said:
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!
Click to expand...
Click to collapse
Flashing SBF's only bricks devices when people dont research what they're doing and they flash the wrong SBF or downgrade from 2.3.4 gingerbread to froyo etc etc... I flashed the 2.3.6 sbf from 2.3.4 just fine.... People just tend to want to run and dive into this stuff without getting the proper information first.
i almost did the same mistake as you ... But i read more and ask users beffore doing something . Try to use Search button and ask don't do any thing on your own .
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.