Database Users

[Q] VISIONARY & Clockworkmod Couple Questions

I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!

you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017

thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!

I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??

[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu

S is off I rooted my phone using the terminal Emulator and that worked fine

When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser

Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot

I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man

slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly

Froyo Software

Here is a link to download the Froyo software so you can do it via the sdcard instead of thru motorolas update program.
http://www.motorola.com/staticfiles...dcards/US-EN/flipside/index.html?pubid=987654

I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !

pamaguin said:
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
Click to expand...
Click to collapse
What was the setup on his phone before the update? Rooted, how much memory avail, etc. Also, did you try both methods, or just this one?

I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.

pamaguin said:
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
Click to expand...
Click to collapse
I wish I had the answer to this. It baffles me as so many have had luck. Hopefully someone will come along that knows more than I.

You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*

Where can I find on how to use RSD lite? And I've tried renaming the file to update with no luck; "installation abort".
JBallin4life27 said:
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Click to expand...
Click to collapse
Sent from my Xoom using XDA App

Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
You can get a stock AT&T ROM here (2nd post) or here (2nd post). I believe that they both point at the same file.
I can state that when I DLed that file it did work for my Flipside.
The hashes for the file I tested were:
CRC32: 92E73801
MD5: 7B529FE7D732EC4E71F5955C887E33A5
SHA-1: 7B49401A107F6DD779DBA0F55DECF473501E554A
Filesize: 196 MB (206,426,725 bytes)
This hashes/filesize are for the extracted sbf file.
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
*you can find RSD Lite by just googling and downloading it*
Will post instructions for using RSD Lite in a second

This guide is for anyone who:
Has ever used RSD Lite, given up at the "Please Reboot this Phone Manually" status, and closed RSD Lite despite being warned: "Application is currently busy. Closing application may DAMAGE the attached device. Do you wish to continue?".
Has never used RSD Lite, but are going to, and want to do it right when you do.
The action described in the first bullet is quite common, so if you've done it, you're not an idiot. I think pretty much every RSD Lite YouTube video shows it being done that way, and it doesn't seem to cause any trouble, so who cares, right? Maybe it's just me, but I'd rather see a result of "PASS" when doing something this critical if at all possible. Here's how to do just that.
Proper RSD Lite flashing procedure:
1. Be sure you have your SBF file somewhere that you can find it. Also, be sure your SBF file is good. If your file was originally zipped, then unzipping it would have given an error if it was corrupted so you're OK. Otherwise, hopefully the source of your file lists its MD5sum. If so, you should verify the MD5sum of your file to make sure it is not corrupt. You can permanently brick your phone with a corrupted SBF (if it's corrupted in just the right place).
2. Plug your phone into a USB cable attached to your computer. Depending on whether or not you have USB debugging turned on, have had your phone attached to the computer recently, etc., you will at least probably hear the "device insertion tone" in Windows, and you may see the New Hardware Wizard install the drivers for your phone. Wait until your computer settles and looks bored before continuing.
3. Power down your phone. Once your phone is all the way "off", slide your keyboard open (on the phone).
4. Summon your best contortionist skills, and press on the "up" direction of the directional keypad rocker (the direction toward the screen -- which could really be to the right depending on how you're holding the phone) [pic]. While holding the dpad in the up direction, simultaneously press and hold the power button of the phone. When you see the backlight of the screen come on you can release the power button and the bootloader screen should appear (it will say "Bootloader" in the upper left corner). You can release the dpad. At the bottom of the text on the screen it should say "Transfer Mode: USB" if your cable is properly connected. If it says "Connect USB Data Cable", then you need to do so.
5. Run RSD Lite. If you're on a version of Windows newer than XP, remember to run RSD Lite as administrator by right clicking its menu choice and choosing "Run as Administrator".
6. At this point the phone should show up in the grid in the bottom half of the RSD Lite window. Give it a minute or two if it doesn't show up right away. Sometimes it takes Windows a minute (or 2 or 3) to let go of the phone and pick it back up again after rebooting into the bootloader. If after a couple minutes your phone still isn't listed in the "Model" column of the bottom section, in RSD Lite, click Config, Device Id Options, and choose "First-Come-First-ServeDeviceId Mode" and press "OK". RSD Lite may say you need to restart RSD -- if so, do so.
7. Assuming that you now can see your phone listed, click the "..." button to the right of the "Filename:" box. Find the SBF file you intend to flash on your hard drive. After choosing the file the right hand File details pane will fill in.
8. OK, this step is where you are going to press "Start" in RSD Lite, but don't do that yet. Before you press Start, read step 9. Step 9 has some timing sensitive tasks. If you do step 9 wrong it's not going to break anything, but you'll waste some time going through an un-needed boot and shutdown of the OS. Once you've read Step 9 and know what you'll be doing next, go ahead and press Start.
9. So far this has all been routine and you're thinking "so what?". This next part is what will get you a result of PASS instead of a warning about destroying your phone. After clicking Start the flashing process goes through several distinct steps. At some point there will be a bit of a delay with RSD Lite showing a status of "Phone[0000]: Waiting for re-enumeration". After that is when the actual flashing happens. When the flashing has completed, RSD Lite is going to issue a "reboot-bootloader" command to your phone. Unfortunately the Droid does not appear to implement the reboot-bootloader command correctly and does a normal reboot instead. If you don't "catch the boot" by holding up on the dpad key the OS will boot. Just before sending the reboot instruction to your phone the status in RSD Lite will change to "Phone[0000]: Phone is being rebooted". On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter. You want to be already holding the dpad key up when this happens. If you followed the instructions for Step 8 you have pre-read this step and knew to be ready for this. If not, your phone is probably already rebooted into the OS. If you miss it and the phone boots the OS it's no big deal (unless the instructions for the particular SBF you're flashing say otherwise). If that happens, let the phone finish its boot, and then just do a shutdown like normal. Then press/hold up on the dpad key and power back on. RSD Lite is patient and will wait.
10. You should now be looking at the bootloader on the phone, and RSD Lite should still be saying "Phone[0000]: Phone is being rebooted". If too much time has passed RSD Lite may be saying "Please manually boot the phone". The "Progress" value on the screen will keep incrementing, and at some point before, or at, 100% the result should change to "PASS". You can now click Close to exit RSD Lite without getting any disturbing warnings.
Congratulations. You've just done a proper SBF flash! The result is not simply cosmetic. RSD Lite is doing a final integrity check after rebooting clean into the bootloader. If you do it the old way (just unplug after the reboot and ignore the warning about destroying the device) you may be just fine, but you may also miss the chance to know your flash didn't go quite right and needs to be redone.
Installing RSD Lite:
First you're going to need a Windows workstation. There is a utility called sbf_flash for Linux that will let you do it with Linux, but that is not the subject of this guide.
Next, grab RSD Lite 4.6 and the appropriate Motorola drivers (32-bit or 64-bit) for your machine. In addition to the preceding links you can get them by going to this link, then double clicking on "rsd_lite" in the right side panel (or single click in the left side panel). [Older versions of the drivers here in case they be useful to anybody: 32 bit or 64 bit.]
Install RSD Lite and the drivers on your computer. If you're running Windows XP, life is good. If you're running Vista or Windows 7 you need to be sure to run RSD Lite as Administrator (by right clicking on the choice in your Start menu and choosing "Run as Administrator"). Hopefully your computer isn't too old. Some machines with older BIOS (like 2002 era) have been known to have USB issues that cause trouble with flashing using RSD Lite.
That's all there really is to installation.

I just posted the 2.2.2 Froyo SBF file in the Flipside Development section. Check that out and use RSD Lite to flash the file...you shouldn't have any problems if you do it correctly. Let me kno if it works or you need more specific instructions

Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.

thehotrod11 said:
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
Click to expand...
Click to collapse
Anytime man!

any one get the white notification led working after upgrade?

data2318 said:
any one get the white notification led working after upgrade?
Click to expand...
Click to collapse
YES OMG its so damn annoying. I thought I had turned it off, but it still shows when getting an incoming call. Turning it off in settings did stop it from flashing if I have a missed call or voicemail tho.

[Solved] bricked defy Step by Step Walkthrough

Original message
:I need some serious help.
I tryed to flash custom 2.3.6 fixed sbf.
which didnt end well, after powerup i would go straight to bootloader with err codes.
so tryed to flash another stock SBF, that ended me in inifinte bootloop with android logo. after 20 minutes in bootloop i gave up and flashed another stock SBF this time it was cellcom israel sbf, it finished the flashing succesfully but now the phone wont powerup at all. not bootloader not recovey.
nada...
I really need your help here, any kind of insights will help. please this is urgent.
BTW: this is a red lense defy, last rom was JB 4.1.1 quarx 30.07 build.
the sbf was supposed to have the same rom.
update 1: managed to finally flash stock, cant enable 3g. phone is still rooted, installing superuser is succesfuly but doesnt control attributes. so 2ndinit currently does not work,
issue solved
Click to expand...
Click to collapse
UPDATE 16/11/2012: links check and updated everything should work.
Solution:
1. first get these files as we'll need all of them: Rsd lite (download and install that),
Motorola drivers (download and install: Here)
JORDN_U3_97.21.51.rar(contains sbf file): http://www.4shared.com/get/xzT3dMXv/JORDN_U3_972151.html
firmware.rar(contains another sbf file): http://www.4shared.com/rar/Ytt5O6--/firmware.html
2ndinit 1.4.2, and 2ndinit 2.3 (can be found here: http://forum.xda-developers.com/showthread.php?t=1032212).
also need the nandroid backup: http://www.4shared.com/file/pVQfB4bF/2011-06-11141427.html
[Optional]
superuser.zip file installing from recovery: http://downloads.androidsu.com/superuser/Superuser-3.2-arm-signed.zip
2. [Optional] I didn't have a router at my house and no signal at my phone and i needed internet for 2ndinit, so i installed a program that turns my wifi on the computer into a hotspot, it can be found here: http://www.connectify.me/
3.First shutdown your phone, hold the Vol down and boot the phone up keeping the volume down pressed. you should come up to a triangle android logo, press the vol up and down key and then tap the screen ( this is a touch screen gui), choose the wipe data/cache and press ok, this should take up to 5 minutes.
4. Now, shut down the phone (pull the battery out and return it back in), Hold the Vol Up button and power up your phone.
you will enter the Bootloader (or BL as its called in the forums) and you should see the phone stating that (usually 9.10 version)
5. after installing Rsd lite, launch it, extract the JORDN_U3_97.21.51.rar and firmware.rar files into root directory (C:\ or D:\ or whatever).
in rsdlite press the
...
Click to expand...
Click to collapse
button and choose the JORDN_U3_97.21.51.sbf file.
connect your phone via a usb cable to your computer, the phone should state its connected. and you should see on the rsdlite window that a device is connected, click on it and press the button :"start".
let it finish and boot on itself (it should do that).
6. [Optional] if you started with low battery now is a good time to charge your phone.
7. transfer the 2ndinit 1.4.2 apk and the 2ndinit 2.3 apk into a folder in your sd card (name it "A" for ease of use).
also extract the 2011-06-11.14.14.27.zip into this folder on your sd card "/clockworkmod/backup/"
8. extract the superoneclick on your computer and launch it, while the phone is connected (should also be in usb debugging mode), press the root button in the superoneclick window and watch the magic, make sure you also install busybox (should be installed automatically when pressing the ROOT button).
9. disconnect your phone, use the file explorer provided with this rom and make sure you check with a "V" to "allow 3rd party apps" in the settings. install the 2ndinit1.4.2.apk file.
open the app after installation and make sure you have internet connectivity, press the install bootmenu option.(now pop-ups should appear regarding permissions, choose "allow" for all of them).
after the green led has turned on, go to settings menu under application/development and turn off the "usb debugging mode".
10. restart your phone and make sure you press the vol down button when the led turns blue during the bootup.
when in bootmenu, choose recovery-> custom recovery.
when in recovery, choose "wipe data/factory reset", "wipe cache", "advanced-> wipe dalvik".
now return to recovery menu and choose "backup/restore"->"restore->2011-06-11.14.14.27".
this should take a couple of minutes.
when its done, go back again to recovery menu, and choose again "wipe cache", "advanced-> wipe dalvik".
power off the phone.
11. hold the vol up button once again and power up the phone to go into bootloader screen.
connect your phone once again to your computer and on the rsdlite window choose the "firmware.sbf" file.
press start and flash it.
12. let the phone boot up, congrats you just revived your phone, root it once again using super one click (if needed), install the 2ndinit2.3.apk.
transfer whatever rom you like (dont try sbf's cause that's how I first got in this mess), reboot phone, go into stock recovery and install that zip after wiping data/factory reset. and ohh well you know the rest.
Good luck.
P.S if you can't or dont know where to find the files take a quick search in the forums and youll find most of them.

Reserved

reserved

when i flash firmware.sbs it takes me back to Android Bootmenu when it reboots please help. thanks

Shouldnt happen, make sure you Wipe Data, and cache, before the nandroid backup and after the nandroid backup.
only then u can flash the firmware.sbf
if the bootmenu still comes up simply choose "Boot-> set default-> normal". and reboot.
if still comes back to bootmenu (and i hope you are talking about bootmenu and not bootloader). install through custom recovery your favorite ROM and don't forget the corresponding Kernel.
good luck!

Is that work with bl7 ???

I've been trying to restore my phone for weeks, up until this thread, I started to think the internet couldn't help me. You are a god amongst men.

OK, banging my head against a wall here; I have 2 defy's. Mine has been to a war zone 4 times, I've replaced the screen (and the waterproof gasket) once, It's broken (the case) but still works except for the fact that the last time I had to flash an sbf I messed up the charging ability with the "macguyver" method.
Now I recently got a pristine looking red lens defy from a friend who said it wasn't booting...It "tried" but never stayed booted long. I tried immediately flashing one of the fixed sbf's with CM10 on it, and ever since I get the bootloader 09.10 code corrupt message.
I've tried the method listed here (by the way the first firmware in OP won't download for me, something about violating some terms of agreement?) the one labeled simply "firmware" downloaded.
Still no joy. Every flash I get all the way through code group 32 checksums match. Everything after that fails. Have tried multiple CEE, Nordic, Chinese, even Defy+ sbf (the new defy has red lens) with no luck.
Likewise when I tried flashing via linux (sbf_flash). The other night after battery out for quite awhile it led me to believe it had started working, and allowed me to get into recovery and wipe everything, but it was all false hope. It still did not boot (motorola M boot loop) and likewise, it still did not flash.
Anyone have any ideas how I can proceed to fix this thing?
I thought I had this thing figured out but obviously I was mistaken.
thanks in advance

I just unbricked my phone again yesterday after trying the latest cm10 sbf with no luck, so i can guarantee this method still works, however the firmware.sbf file is really needed and also the nandroid backup, so here's what i'll do:
1. i'll check what links are broken and reupload the necassery files.
2. I'll clean the the first message and update the links
so check back in about an hour

Thanks a lot for posting this. Tried to restore my phone using lot of other posts since the last 3 to 4 days days, but all in vain.
Was anybody able to install CM10 over this? After the installation, the phone is going into boot loop.

Thanks rtk217 for starting this guide very useful for noobs...
I've made some video tutorials using a few of the guides in the forums here...
hope it helps someone...
Its a complete step by step.
Part 1 of 4. This part deals with preparation of all the required files to successfully complete the custom rom installation.
http://youtu.be/jMAlys2_KG4
Part 2 of 4. How to restore Defy to default
http://youtu.be/6SUysKZ2E5Y
Part 3 of 4. How to root using SuperOneClick and install clockworkmod.
http://youtu.be/hd3_SRbkUWw
Part 4 of 4. How to install 2ndinit recovery and install CyanogenMod 10 Jelly Bean 4.1.2
http://youtu.be/gNPacGesWOI

I am still not able to install CM10. I had bricked my phone a week ago, so I followed this post using the below steps:
1. Flashed with JORDN_U3_97.21.51.sbf.
2. Installed 1.4.2 Sndinit..
3. restored the nandroid backup 2011-06-11.14.14.27
I am able to restore Froyo...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?

k.manojraja said:
I am still not able to install CM10. I had bricked my phone a week ago, so I followed this post using the below steps:
1. Flashed with JORDN_U3_97.21.51.sbf.
2. Installed 1.4.2 Sndinit..
3. restored the nandroid backup 2011-06-11.14.14.27
I am able to restore Froyo...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?
Click to expand...
Click to collapse
Have you got a Defy or Defy+ as you are trying to install the cm10 zip for MB526 (Defy+)

I have a defy mb525.. The one i tried to install is a 2nd boot build that is common for both mb525 and mb526

k.manojraja said:
...
Now I am trying to install CM10 using the following steps:
1. Install 2.3 Sndinit
2. do a full wipe
3. install CM10-20121205-NIGHTLY-mb526.zip
4. Install Defy-Gapps-CM10-20121109-without-Voice.zip
once rebooted moto logo appears.. the LED turns red and again tries to reboot.. again reboots to moto logo and the same thing happens!
Can somebody help me?
Click to expand...
Click to collapse
Why are you using 2ndInit 2.3???
All the guides and FAQs will tell you to use 2ndInit 1.4.2

hey i have the same problem did you fix it?
k.manojraja said:
I have a defy mb525.. The one i tried to install is a 2nd boot build that is common for both mb525 and mb526
Click to expand...
Click to collapse
hey i have the same problem did you fix it?

Thanks ...
Hay, Ur are a genie to me.. I tried so many mods after my imei no is gone. Wifi not working, issues with signal catching.. Now with your step by step guide i was able to overcome all of those... Thank you very much.

cmcooper123 said:
hey i have the same problem did you fix it?
Click to expand...
Click to collapse
Yep... Please see the thread http://forum.xda-developers.com/showthread.php?t=1618718&page=32
Look at pages 31 and 32...

k.manojraja said:
Yep... Please see the thread http://forum.xda-developers.com/showthread.php?t=1618718&page=32
Look at pages 31 and 32...
Click to expand...
Click to collapse
but if i flash defy plus firmware on a defy mb525 wont that brick it?
---------- Post added at 12:05 PM ---------- Previous post was at 11:24 AM ----------
cmcooper123 said:
but if i flash defy plus firmware on a defy mb525 wont that brick it?
Click to expand...
Click to collapse
lol my bad it did brick it kind of
flashed DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
then JORDN_U3_97.21.51.sbf
now it has a black screen but in boot loader mode sigh
any way this is were i am at:
http://forum.xda-developers.com/showthread.php?t=2032711
SIGH

cmcooper123 said:
bwithut if i flash defy plus firmware on a defy mb525 wont that brick it?
---------- Post added at 12:05 PM ---------- Previous post was at 11:24 AM ----------
lol my bad it did brick it kind of
flashed DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
then JORDN_U3_97.21.51.sbf
now it has a black screen but in boot loader mode sigh
any way this is were i am at:
http://forum.xda-developers.com/showthread.php?t=2032711
SIGH
Click to expand...
Click to collapse
I am really not sure if you have read the posts properly. I had no problems in flashing the defy plus sbf. The defy plus sbf that I gave you was a bl6 version and you can never downgrade to froyo.
97.21.51 is a Chinese éclair with bl5. 2nd boot builds were not working on bl5.

Kinda n00bie Guide

Ok all, help me out here too, this is my very first guide EVER!
If you need to root your phone ONLY:
Google search for Super1Click,
Place phone in debug mode, Settings/Applications/Development/Android Debugging
Plug phone into computer using any USB cable, wait for drivers to install, look to see if a device called Android ADB something installs
If not, Google search for Moto Driver Helper, install and run that, plug phone back in.
Open Super1Click, click root.
After it's done, unplug and reboot phone.
If you want to install apps from anywhere else besides the Google Play Store
Root phone, see above
After reboot, plug phone back into computer and then click [Allow non-market apps]
Reboot.
All set.
If you want to install Clock Work Mod Recovery, aka CWM Recovery, CWM, Advanced Recovery, etc.
1 click method to root and install CWM at same time
To install a custom ROM
Find ROM
Download ROM
Download the gapps.zip for your ROM (eg gappscwm7.zip for Gingerbread, gapps9.zip for Ice Cream Sandwitch, etc.)
Have root and CWM o phone, see above on how to do that.
Pace the ROM and gapps.zip files on your SD Card either with the phone in Disk Drive mode or with a USB Stick or whatever.
Boot into recovery mode ONLY THIS EXACT WAY: Power off phone wait for BLUE LED, hit the VOL. DOWN Button.
Push VOL. DOWN to select (Recovery)
TAP the power button.
TAP power button on [Custom Recovery]
Using the VOL. UP and DOWN buttons, select (Wipe data/factory reset), TAP power button to enter
After that, do the same thing but select (Wipe cache partition)
Last go to (Advanced), then (Wipe Dalvik Cache)
After that sometimes I'll do the (Wipe Battery Stats), but you don't have to if you don't want to.
Then click (Go Back) and then go to (Install zip from sdcard)
(choose zip from sdcard)
Then select your ROM FIRST, then install
Then after do the same thing again, (Install zip)..., this time install the gapps.zip (eg mine is gapps-gb-20110828-signed.zip, for Gingerbread, AKA CM7, yours can be the same for CM7, of if installing ICS, AKA CM9 or JB, AKA CM10, It'll look like mine but have ics or jb or something in place of [gb])
Then click (Go Back)
Then click (Reboot system now)
Let phone reboot, you should see a blue led and then either a green (good), yellow (might work) or red (bad rom) led.
If it was green, your good.
if it was yellow, it might work.
If it was red, try again from turning off phone and pressing VOL. DOWN at BLUE led.
IT WILL TAKE UP TO 10MIN FOR YOUR PHONE TO BOOT THE FIRST TIME YOU INSTALL A CUSTOM ROM, BE PATIENT.
If you still see the boot up logo after 10min, pull the battery and put it back in, turn on phone again and it should boot fully.
If your stuck on red (M) logo, see below To return phone completely to stock, and retry from To Root your phone.
If you have any other issue or get stuck somewhere, POST YOUR ISSUE BELOW.
To unlock your phone (This is NOT the same as rooting your phone)
First and foremost, you'll need ANOTHER SIM CARD , not SD Card, SIM CARD ,
Fist try to call AT&T and ask them for your network unlock code,
If that doesn't work then either Google SIM Unlock code or ask around here for help in getting it. You might try this, or this if you know Russian or post below you need help
After that, reboot phone.
Then pull battery, change out your sim card with the other carrier sim card (anyone but an AT&T simcard) and it'll ask you for the code, put it in and your all set.
I will finish and update this as I have time.

I was going to create a guide for newbies sometime ago, but my PC got broken and Im not working now to fix it.
Good to see it, there lots of new users trying to get something from zero to update their phones.

josuearisty said:
I was going to create a guide for newbies sometime ago, but my PC got broken and Im not working now to fix it.
Good to see it, there lots of new users trying to get something from zero to update there phones.
Click to expand...
Click to collapse
Ya well it's not even finished yet. If you look at it in full, I left out acouple of sections that should be there. Work in progress, just like most of my life. And I need to fix the links too.

[Q] Milestone 2 - CM11 - Update Failure - Phone not booting up

A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David

Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!

Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.

Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!

More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David

Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.

Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.

Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.

1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David

david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11