when i got my moto defy for xmas last year, i had my older brother root it for me. i really had no idea how to safely use root, but i liked being able to overclock and all the other features. the phone was a little buggy just because it was on 2.1 and no updates yet. once an update came out, i installed it and got a great performance increase. later, i realized that it was not working right. whenever i hold down an on-screen button, the touch sensitivity "timed out" after only about 1.5 seconds, unless i kept my finger moving around on the screen. and every few times i reboot the phone, this glitch goes away until i reboot again and then it is back. root was also taken away, and none of the one click roots work. also, when the 2.2 update came out, i got the error message when rebooting after installing the update and it did not work. i tried wiping the phone several times, no luck. i am now interested in fashing a custom rom and rerooting. would this fix it? there must be a special way to do it since my phone is so messed up. i would like 2.2 or 2.3, and 720p vid would be cool too. the version i have now is 2.1.1, so can anybody suggest a rom that is stable and will work ok?. one more question, when i flash a rom, will it leave my apps and settings alone or do i have to start over?
Have you tried using SuperOneClick to root the phone? (You'll need to install the Motorola drivers for it to work.)
In most cases, you will lose your apps and settings when you flash a new ROM. But, if you figure out a way to root it, you can back everything up in Titanium Backup first, and restore it afterward.
If you just want to start from scratch, try wiping everything in the stock recovery. To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition".
If that doesn't work, I'd recommend flashing a new Froyo sbf using RSD Lite. Here's a quick tutorial:
1) Install the Motorola drivers and RSD Lite on your computer. See this guide for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
2) Download the sbf file that you want to flash, and save it to your PC. Many sbf files can be found here: http://forum.xda-developers.com/showthread.php?t=966537 WARNING: If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again.
3) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
4) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete. Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
Then you should be able to root, install custom recovery, and flash custom ROMs to your heart's content.
Good luck!
Thanks! Sorry to be a noob, but how do I know if a rom /sbf will work? Doesn't it matter what android version I have now? 2.1.1 is it
Sent from my MB525 using XDA App
Most custom ROMs for the defy require that you upgrade to Android 2.2 (Froyo) first. I can explain how to do that, if you like. What country are you from, and what cellular service are you using?
Before doing anything to your phone, you should read this guide: http://forum.xda-developers.com/showthread.php?t=1216982
Take a backup using titanium backup. This takes Care of all app and games. Then flash froyo. Go hd to install a custom rom like cm7. Guides are there for this. Restore all app and games with data from titanium backup
all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.
The best base (Froyo 2.2.2) for using a custom rom :
http://sbf.droid-developers.org/umt...RDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf.gz
Flash and enjoy CM7, Miui...
But honestly you need to read a little bit before... Or I can explain in french to you if you prefer... :-D
ritchrocko said:
all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.
Click to expand...
Click to collapse
If your DEFY has a greenish-yellow camera lense (as most do), you won't get 720p video capability no matter which sbf you use. (Unfortunately, it's a hardware limitation.) Most custom ROMs will enable you to take widescreen videos, though.
You don't need to use a T-Mobile USA sbf, by the way; you can use any Froyo (Android 2.2) sbf you want (except for Chinese ones, which will burn out your camera flash). You just have to change the cellular radio baseband afterward, to match the frequencies used by T-Mobile USA. That's easy to do; just use the "DEFY baseband switcher" app: http://forum.xda-developers.com/showthread.php?t=1052745 (Many custom ROMs, like CM7, already include the basebandswitcher app.)
Since you don't want to search through the forums for a guide on how to flash an SBF, here's one I wrote for a friend a while ago:
Flashing SBF firmware with RSD Lite
Follow this guide to flash firmware files (with .sbf filename extension) on the Motorola DEFY. This is useful for “de-bricking” a phone that won’t boot (provided the bootloader still works), or if you want to do a clean install of the Motorola stock firmware. I don’t recommend flashing SBF files unless absolutely necessary, however, since the process is dangerous: there is a slight possibility that your phone could become “hard-bricked” if something goes wrong. (A phone is hard-bricked when you can’t even access the bootloader to flash new firmware.) It is much safer to flash or modify firmware using ClockworkMod custom recovery, which doesn’t mess with the bootloader. (See step 3 for more info.)
Before flashing any new firmware on your phone, I strongly recommend reading this Beginners Guide: http://forum.xda-developers.com/showthread.php?t=1216982
WARNINGS:
A corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a “hard-bricked” phone (i.e., a phone that can’t even be restored by flashing new firmware, because you can’t get into the bootloader). It is recommended that you flash your phone from a laptop with a fully charged battery, to reduce the risk of losing power while flashing. Use good cables, and be sure that the PC doesn’t go to sleep during the flashing process.
If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again. (You can, however, install DEFY+ firmware without losing downgradeability, using the “fixed SBF” method. See this guide for more information: http://forum.xda-developers.com/showthread.php?t=1216982 )
The Chinese version of the DEFY has a different kind of LED for the camera flash. Using the camera flash with that firmware can permanently damage the LED.
Before installing any new firmware on your phone, backup your stock firmware, so that you can return your phone to its original state in case you ever need to send it to Motorola for repair. The firmware for the US T-Mobile version of the DEFY was never released as an SBF file, so you won’t be able to restore the phone to its original state unless you have a full system backup of the stock firmware. (See note at step 3 of the guide below.)
1) Install the Motorola drivers and RSD Lite on your computer.
See these guides for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
http://forum.xda-developers.com/showthread.php?t=897445
2) Flashing new firmware using RSD Lite will erase everything on your phone’s internal memory (but not the SD card), so backup your contacts, settings, and any apps you’ve downloaded. I recommend using Titanium Backup, which is available free on the Android Market.
Note: your phone must be rooted before installing Titanium Backup. You can root the DEFY using SuperOneClick. Rooting the phone voids the warranty, but you can use SuperOneClick to un-root it if needed. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
3) Download the sbf file that you want to flash, and save it to your PC. If you are doing a “clean install” of CyanogenMod 7, I recommend using the 3.4.2-179-2 CEE DEBLUR sbf. Links to download it can be found in this thread: http://forum.xda-developers.com/showthread.php?t=966537
It would be a good idea to keep that file on your PC, in case you ever need to de-brick.
4) Optional step: before flashing an SBF file, it is a good idea to wipe data and cache in the stock recovery. (I usually forget to do that, though, and I haven’t had any problems.) To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition". (At least, that is the procedure on Android 2.2. If I remember correctly, on Android 2.1 you had to tap somewhere on the touchscreen to get the menu to display, and the touchscreen was also used to navigate the menu.)
5) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
6) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. (WARNING: read the above warnings about file versions and downgradeability.) After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete.
7) Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
8) Root the phone using SuperOneClick. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
9) If you're not going to install a custom rom and you used an sbf that is not for T-Mo USA, you'll have to change the baseband frequencies. Install the baseband switcher app: http://forum.xda-developers.com/showthread.php?t=1052745 Open the app and click on the “Americas” tab, and select one of the “US T-Mobile” options. (The “US T-Mobile 3.4.2-107-9” option works well for me.) The phone will have to be rebooted again.
Related
Ok, I installed Clockwork a while ago, then removed it and unrooted (I no longer needed root access, and I'm not doing any image flashing or anything that requires it). But after removing clockwork, it still boots to that first when I reboot my phone. In case if I ever have to take my phone in to VZ or something, how do I stop it from booting to that? I'm guessing it's not just a normal app, since I've reset to factory since then to try to resolve another issue, and it's still appearing, so I'm guessing it installed itself into the ROM.
I basically rooted my phone originally to install Titanium Backup before doing the factory reset, then I was thinking of trying some custom ROM's, but I decided not to (other than a performance increase, there's nothing else I really care about right now that custom ROM's would provide). So I installed Clockwork Mod and everything else RLM703 listed (http://forum.xda-developers.com/showthread.php?t=814299&highlight=guide), then removed everything after I decided not to mod it.
I can understand your concern on the not flashing, however if you do not flash i think you also still have the Superuser app (even ifyou dont have root rights) that itself would also void your warranty. The easiest, fastest, and safest way is to Flash it using the Method below.
Go To (droid-life .com /2010/09/21/how-to-return-droid-x-back-to-android-2-1/)
((**As a new user i cant post outside links so delete the spaces after life com in order to get the proper working link.))
**
You will download 2 things. The SBF for 2.1 (Which afterwards you can use OTA to reupdate to 2.2).
RSD Lite: This program is used by Motorola to flash phones so its not some unstable application that will mess up.
After you install the drivers, THEN install RSD Lite. You must Run RSD Lite as an administrator. Shift Click RSD Lite and choose Run as Administrator (Even if you are on an administrative account). Afterwards you just navigate from RSD lite to where you have your SBF Saved, Boot your phone into bootloader, then press start. Takes about 5 minutes and you are back to a brand new Droid X.
Like i said i understand your concern on this, and im deeply sorry if you get a rare case and it does decide to mess up, but i just flashed my phone 3 times yesterday using this method and never had a problem.
Hope this helps!
Ok, I know I created a backup through ROM Manager before I stalled Clockword Mod Recovery, but now I can't find it... However, I've been having some minor issues with my phone ever since I updated to 2.2, so maybe I'll just find a stock SBF and flash back to that... That link I posted has a droid x guide, with a link to a stock 2.2 SBF, so I can just grab that and flash it tonight or something. Or even just download it at home and keep it in case if I need it down the road...
Hi guys,
I'm a bit lost and unsure what to do.
I installed GummyJar, and like an idiot, didn't read that I need to be on 2.3.320 or 2.3.340.
I was previously on ZapX for 2.2 (purchased phone in early October). So I'm not sure what to do. Is there an SBF that will directly put me on 2.3.340? Would it be wiser to flash to my original SBF (the_gift2.zip I believe), and let my phone automatically get the OTA update?
I'm not really sure what the best thing to do is.
Thank you for any advice and help.
Did you create a back up before you installed Gummy? I know that is praobably a stupid question since you are asking how to SBF -but I thought maybe you didn't think about restoring your backup?
How to perform the sbf:
I did this. It worked for me. I TAKE NO RESPONSIBILITY IF THIS DOES NOT WORK FOR YOU OR IF YOU MUFF IT UP.
ok- so here is the link that I used as a guide - IMPORTANT!!! - the directions are for restoring 2.1 so you do not do some of the steps! They were the best I could find. I followed them except for things that did not apply.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
You probably have already done this.
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9 download here...
http://dl.dropbox.com/u/7782384/RSD%20Lite%204.9.rar
3. You will need to patch this after installing. There is an .ini file included in the folder that needs to be placed in your install directory. /Program Files/Motorola/RSD Lite
I used 4.9 and did not have to patch any files- the above step was unnecessary.
4. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file. Make sure you use the right sbf file or you will really be hosed!!! if you are on 2.2 you can get the full sbf file from here...
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
5. Unzip the SBF file to your desktop
i did not unzip mine to the desktop- i put it where i stash my android files- it made no difference.
6. Run RSD Lite, and click the “…” button, then find the SBF file that you just unzipped to your desktop and select it.
Starting here i followed the directions to the "t". Went through all the steps.
!!!!!MAKE SURE YOU START WITH 100% BATTERY!!!!!! It takes a long time and if your phone dies during the process it is a nightmare.
7. Plug your Droid X into your computer and power it down
8. Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
9. After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
10. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
11. When the flashing is complete, unplug your phone
12. The Droid X will likely not boot up all the way, so pull the battery out
Put the battery back into the phone and reboot into Recovery mode ( Hold the HOME button and press POWER until you get an exclamation mark. Release the HOME button and press the SEARCH button)
13. Using the VOLUME UP/DOWN buttons, navigate to “wipe data/ factory reset” option on the screen, and press the CAMERA button halfway down to execute.
When complete, choose to reboot your phone
14. It takes a while. Hope this helps. And I hope it goes smoothly. It was nerve racking for me. After you have finished the process you will not be rooted.
15. good luck.
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
EtherBoo said:
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
Click to expand...
Click to collapse
Well- of everything goes right you should be able to go to your phone settings, scroll down to the bottom to "About phone", then "System updates". You should be able to manually update from there.
If you get a "your device is up to date message," then something went haywire. Hopefully that won't happen.
Oh yeah - here is the link for "z4root" -you can use it to root your phone after the update...
http://dl.dropbox.com/u/7782384/z4root.1.3.0.apk
If your phone won't manually update, there is an update.zip floating around here. I have it - but not on the computer I am currently working from -sorry.
Again I want you to know - I am not an expert at this - if something goes wrong I will not be able to help you fix it (probably). I just followed the guide and it worked for me. So if something happens when you follow the guide -I am sorry but I won't be much help.
Thank you. Everything took about 2 hours (SBFing, downloading and installing update, reinstalling apps, etc), and I have the newest Kernel version from the OTA update, and GummyJar 2.5 back on.
I had a bit of trouble SBFing, it kept failing for some reason, but I found a fix via googling around the various Droid forums.
Thank you again, you've been extremely helpful.
Help with Droid X in Buffalo NY
ive tried everything I could for almost a week now.... Stuck in Bootloader Screen 30.04 Err A5,70,70,00,1F MEM_MAP Blank Service Reqd Battery Ok OK To Program..... I came to a Droid X last week from a Rooted for over a year Droid 1 with never a problem flashing... With new Droid X tried to flash Gummy Jar last sat without a wipe ( I know my stupidity thought coming from stock phone could get away with it trying to rush but boy was I wrong) after being stuck at loading gummy jar icons tried to factory reset... been stuck at the bootloader screen since.. tried flashing 1.13.6.2_1sbf and 2.3.32_1FF sbf... got newest drivers and rsd 4.8... ran as administrator... phone never shows either... got it once to do something in rsd saying phone was being programmed with 2.3.32 but when it said finished waited hours never rebooted .... stuck dont know what to do....anyone local want to give it a go email me please [email protected] or try to walk me through what i have to do step by step.... thanks
If you just look for the bold font, you'll probably find what applies to you. -I tend to ramble alot so hopefully that will help you all cut through my crap.
Hello everyone, since you've come here you're probably looking for a way to fix your phone. There seems to be alot of new members popping up lately, all asking the same simple questions across various forums. Hopefully this thread can become a 1 stop shop of information on how to fix your bricked MS2, and information on what rom is compatible with what kernels.
A round-up thread can be found here but I'm pretty sure it is in need of an update - though some of the basics there are still relevant. <<<< PRETTY IMPORTANT THREADS IN THIS LINK
Droid 2 roms do not work with your Milestone 2. Period.
If you have updated to Gingerbread (officially), alot of the roms for the MS2 will not work on your phone anymore. Please refer to the version compatibility at the end of this thread to see what you can use. This is because the Kernel is upgraded and cannot be downgraded. Most of our roms run on an older kernel.
As of yet, no-one has permanently bricked there phone by flashing the wrong ROM or SBF file. This is due to the locked bootloader - no matter what you do you can't get rid of it and can allways flash back to stock ROM. If you think you cannot access bootloader mode and only get a black screen, fear not! It is actually in bootloader mode, just you can't see it. RSD-lite should recognize it.
Can't flash with RSD lite/phone still won't boot
run RSD lite as administrator
restart your PC
get a different version of RSD lite (preferably newer - downgrade if on newest)
re-download SBF file.
Check you are using a correct SBF - if you updated to Gingerbread (officially) you MUST use a Gingerbread SBF. Froyo users can flash whatever, but I strongly recommend you dont flash a Gingerbread SBF
A guide to fully restoring your MS2 to "out of the box" settings can be found here
I can't access bootloader: Some side information on the bootloader - if you have let your battery drain too low, it will not work. If you can't seem to access bootloader mode and just get a blackish grey screen - it is infact in bootloader mode and RSD lite should recognize it (see restore guide) A bricked MS2 will not charge. You will either need a wall charger than charges the battery directly (not inside the phone), or you can use the MacGyver method of charging it directly with some wires directly from a power source (something low voltage 3-5v's or so). For more information on this, please refer to google . I do not recommend the macgyver method - I have used this method before and I swear my battery has never been the same since. Plus the obvious dangers of playing with electricity if you don't actually know what you are doing.
boot loop or moto logo then black screen when booting
Potential causes are:
You may need to factory reset by accessing recovery. It is hold X on froyo, then when the triangle with the ! appears, you press @. I believe it is the same for gingerbread, but you press vol up and down when you get to the triangle. Please correct if i am wrong .
Corrupt SBF file - try a different one.
Incorrect SBF for the kernel you are on. If you OFFICIALLY updated to gingerbread, you can only use gingerbread roms and sbf's.
Version compatibility
Custom ROMS for stock froyo users (still on froyo kernel or CH-GB leaked kernel):
Cyanogen Mod 9 (tezet)
Cyanogen Mod 7 (tezet)
Cyanogen Mod 7 (endless7 - defy port and mod for tezet's cm7)
MIUI (will5)
Argen2Stone (santiemanuel)
INSTALL INSTRUCTIONS (froyo users)
CM7/CM9/MIUI install instructions can be found here - be sure to download the "all other users" version of CM9
Argen2Stone install instruction can be found here
To install endless7's CM7 mod, first install for tezet CM7, then flash the .zip of the mod in CWM.
There are others but I'm not sure if they are relevant any more - certainly hasn't been any updates in a long time.
Custom ROMS for official Gingerbread users:
Cyanogen Mod 9 (tezet)
Cyanogen Mod 7 (endless7 - defy port ONLY)
Argen2Stone (santiemanuel)
INSTALL INSTRUCTIONS (Gingerbread users)
CM7/CM9 install instructions can be found here - be sure to download the "European GB kernel" version of CM9. CM7 will need to flash the fixed SBF with RSD lite afterwards (contains the kernel you require to boot your phone)
Argen2Stone install instruction can be found here also be sure you do not flash any fixed sbf as you are already on a compatible kernel. If you already did, or didnt come from stock gingerbread or get a bootloop, then try flashing the fixed sbf with rsd
If these instructions for GB seem wrong, please let me know - This is just what I've gathered from barely paying attention to it. I have not upgrade (/downgraded really) to official GB so don't know from experience.
Misc. Troubleshooting & Additional Information
GPS not working - Download faster fix from the market and select an appropriate server - the rom you are on is probably set to a different country.
Data not working - Check you have the right APN settings - often the default settings appear correct, yet have some errors (eg will put * as password and username, hen it should be blank.). Just google your country and provider for you correct settings.
Apps force closing: try data+cache wipe and dalvik chache wipe (you will loose all data though)
ACCESSING RECOVERY - CWM or Stock
You can enter Clockwork Mod recovery by pressing the volume buttons when the notification LED flashes in boot up.
If you can't seem to access CWM, try entering Moto's recovery by holding x while turning on the phone and factory reset in there. (press "@" on froyo and "volume up & down" on gingerbread to get past the ! in the triangle.
If you can't access either of these, all thats left is restoring via RSD-lite and trying again.
Useful Links:
Official Firmwares
Battery Calibration
If anyone has any suggestion to improve this thread, additions, or corrections, please comment and I'll edit if fitting .
Cheers - hope this can help a few people.
Special thanks goes out to tezet, endless7, will5 and santiemanuel for bringing us these custom roms, and to Mr. Clown, Mikevhl and EGZTHUNDER1 for your reference threads and guides I've linked to.
Ok hello all, I have a bricked atrix here (new user) and cannot restore the previous firmware I backed up.
What I did step by step is:
I followed this guide to unlock phone and install CWM recovery mod. ( I backed up my factory "firmware" )
After that I installed Neutrino ROM 2.2 from here but it was a bit buggy and I wanna revert to my factory settings.
When I try to restore the old firmware checking md5 and bootloader restore ok, system gives me a message: "Error while restoring /system"
At some point I also installed "recovery-en-goapk-0630-1029" which seems just another recovery tool (dont know if this caused the issue)
I also have RSD Lite and the original ATT's 4.5.91 .sbf file but that cant work as well. Once I hit RSD mode on my phone and hit start on pc, phone says after a couple of mins: sec_exception: febe, 35, 35 and then doesnt progress anymore.
By the way my phone is European and it came with 2.3.4 preinstalled out of the box, I just wanna revert it back! please help!
what's that "sec_exception" about? I always get this when I try to RSD-mount the .sbf from ATT 2.3.4 Pudding
RSD tells me a short after: Failed Flashing Process. Phone [0000] . Phone did not re-enumerate after RAM-downloader was sent (0x703E); phone connected (Result FAIL)
First of all, I don't think you should be using an ATT sbf file with your European Atrix. Not a good idea; they are not the same.
Secondly, using a sbf and RSD is tricky business and should be avoided if possible.
If you want to return to stock I suggest using the tool in this thread:
http://forum.xda-developers.com/showthread.php?t=1421522
It is dead simple to use.
since I'm new to this (got some good pc experience tho) I wanna keep things clean and organized, so what can I do to clean previous installations , zips , rsd sbf mounting etc. As I see this, the phone's memory has 2 partitions, 1 for system and 1 for apps? Correct me if I'm wrong I'm just starting to get familiar with all this thing
If you follow the link above it will wipe everything on the phone and return it to stock. You will need to wipe your SD card yourself however.
Sent from my MB860 using XDA App
I had this with all recovery iv try I found out its because the system.ext3.tar backup is over 300mb the only the only. Way back from this was to ever flash a European gingerbread sdf or use fruitcake
the way I got past this was to deodx my rom so it is under 300mb
following the above link is the best method. please do so.
the method is perfect indeed, my phone is back to normal except that AT&T submenus and logo. Is there any program to view root folders and clean previous installations / garbage files? Any guides on what should be left off - uninstalled? (Neutrino 2.2 custom ROM had a file explorer that could navigate between root folders and sd storage
thanks again
i got the same issue but my phone doesnt turn on at all, just the led light in green then it goes off
have you tried to pull the battery off? Do you see the Motorola logo or just black screen?
Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!
Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!
Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)