Related
I had apex 1.4.1 on my Droid 2 and I had the green evolution theme on it. I went to reinstall the 1.4.1 so I would have it without the green theme because I had other mods to install to it. I did what I wanted to and then I rebooted, It was stuck at the apex boot screen which is extremely annoying and it kept replaying and the phone simply would not turn on. So I reluctantly wiped the phone. I start it normally and it shows the motorola logo and then the screen stays black. So I'm guessing there is literally nothing on the phone. When I go to bootloader, my computer recognizes it as an OMAP flash drive. I'm completely lost and I don't know if there is anything I can do to fix this. Can someone please help me? Thanks.
SBF is your best friend for Motorola phones.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
Latest Moto Drivers:
http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
If you can get to the bootloader, then your phone is not bricked.
Also, before I ever attempt to root a device I've not rooted before, I always search and find a recovery method for that phone. In Motorola's Case, it is SBF files. In HTC's case, its RUU files.
ALWAYS ALWAYS ALWAYS find a recovery method for your phone before you root it. Also, read EVERYTHING you can about rooting your particular phone before rooting it, that way you would already know how to fix it if you mess up.
My computer won't let me transfer files to my phone, will this help?
I tried to follow what it said and I have no idea what I'm doing. appreciate the help though.
jakeg2012 said:
I tried to follow what it said and I have no idea what I'm doing. appreciate the help though.
Click to expand...
Click to collapse
Well, I don't see you being able to get your phone back in working order otherwise.
Its really easy to do.
1. Download and install RSDlite 4.9 on your computer. (download from here h t t p://www.mobile-files.com/forum/showthread.php/763-RSD-Lite-4.9)
2. Download the latest Moto drivers and install on your computer.
3. Download the SBF file and put on your desktop.
4. Plug your phone into your computer, and your phone should turn on and be in bootloader mode (black screen with white text)
5. Run RSDlite.
In RSDlite, there should be a box with "..." Click that, and then choose the SBF file from your desktop. Hit start, and let it work. DO NOT shut off your computer or unplug your phone while this is running.
When RSDlite says its finished, unplug the phone, turn it off.
Now you need to boot into recovery. To do this, hold "x" on your keyboard and the power button. When a screen with the triangle comes up, hit the search button on your keyboard (magnifying glass). Choose "wipe data/factory reset". When thats done, select "wipe cache".
Now reboot the phone, and it should boot up normally. You will need to reactivate your phone, which you should be prompted to do in the setup.
I did everything. Everytime I put the sbf file (which shows up as a zip file) into a folder I look for it through rsd lite and I can't find any zip files/sbf files I've downloaded. What do I do now? Am I doing something wrong? sorry for being a pest btw.
Your not being a pest
You need go extract the .sbf file from the zip folder to somewhere like your desktop. Then find it in rsdlite
Sent from my Liberated DROID 2
I can't find a working sbf file. Every time I use it I get FAIL.
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.
Defy sick please render aid!
Had CM7 but wanted to try CM9, easy enough clear, format, flash poof -
Installed cm9 nightly and gaps, everything worked just fine and fluffy. I have done this a few times before, but...
Installed the Motoizer App- still all good
Then I decided to install the Motoizer optimizer pack it said it was going to reboot, and it did. But now it does not make it past the cm9 boot animation screen, the animation just runs and runs… (not very exciting or useful, but it is cool looking)
Pulled battery after waiting a long time, power+down yields the little droid and the triangle with the exclamation point. If I press the middle of the vol up/down (both) then get the recovery utility. Not a lot of options here, I can install a update.zip, factory reset (clears/formate) or wipe cache partition.
Oh and PS, yes I have googled, searched and waived a dead chicken over my sick Defy…so any suggestions?
Thanks,
Just a guy with a sick Defy…
u don't come into bootmenu? only stock recovery?
ur can do a lot of things.
flash the found stock recovery that flash every update, original or not.
or u flash a modified sbf with integrated CM9 or CM10.
all that found in xda
Jelly powered.Defy
Yeah, I saw many posts, they all lead down the sbf road, I was hoping I could fix it with out sbf-ing it, but that is what I ended (I am in a bit of a time crunch right now) up doing, dang, Oh well, no biggie. The phone lives, not sure what happened with motomeiser though, it seemed like a good idea at the time. Well now I have a copy of RSD Lite, which I did not want to ever have to own... If CM9 pans out I will likely stop there and go static since I have too much other stuff to get done.
Thanks anyway.
Enjoy - Darknetone
if u use this -» http://forum.xda-developers.com/showthread.php?t=1787541 recovery that only rewrite the stock recovery, and if ur re-signed ur CM9 zip u can flash it over and nothing from ur data is gone if I'm right.
Jelly powered.Defy
Can you help me please?
I successfully installed framaroot. Then I installed 2ndInit. Green led: I reboot. No blue led. After a couple of reboots, pressing vol- brings me to the little droid and exclamation mark screen. I can't do nothin but remove the battery.
What can I do? I was going to flash twrp and then slimkat. Android is 2.1.
EDIT: In case I follow the RSD suggestion: does this replace the twrp step? Can I install slimkat afterwards?
vipervault - you shouldn't need to flash an sbf if your phone boot up fine, only if it's in a boot loop (red moto logo)
It just sounds like sndinit didn't install properly.
Verify you properly rooted your device: f-droid.org/repository/browse/?fdfilter=super&fdid=com.abcdjdj.rootverifier
If that checks positive, install an updated su binary: f-droid.org/repository/browse/?fdfilter=super&fdid=com.koushikdutta.superuser
Then try installing sndinit again, make sure you have the latest version, 2.3.
danish1984 said:
vipervault - you shouldn't need to flash an sbf if your phone boot up fine, only if it's in a boot loop (red moto logo)
It just sounds like sndinit didn't install properly.
Verify you properly rooted your device: f-droid.org/repository/browse/?fdfilter=super&fdid=com.abcdjdj.rootverifier
If that checks positive, install an updated su binary: f-droid.org/repository/browse/?fdfilter=super&fdid=com.koushikdutta.superuser
Then try installing sndinit again, make sure you have the latest version, 2.3.
Click to expand...
Click to collapse
Thanks @danish1984. 2.3 is the latest version of what? I wrote I have android 2.1; your f-droid link points to com.koushikdutta.superuser 1.0.3.0.
For everybody who doesn't see the blue led: 2ndInit installation did not work. Install it manually as per this thread.
Some notes I've just made a few moments ago.
I was on Quarx CM9 ICS 4.0.4, and so decided to re-live how I installed 2ndInit as I had a few problems.
(and wanted to make log of what I did a day or two ago, only bought 2nd hand Defy a few weeks back, £8.00 UK).
Below I flash original full SBF file, to get back to Eclair v2.1-update1. (Had only previously flashed Fixed SBF's, ie minus CG 31 and 39)
I got my Motorola Defy MB525 (Green Lens), retail UK, Eclair v2.1-update1 stock,
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf.gz
from:- https://firmware.center/firmware/Motorola/Defy (MB525)/Stock/
MD5: b42848509d1fb19d746185b79b8e1816 (Did Google search on the MD5 and check matches with droid-developers.org MD5).
(Google HashCheck or HashMyFiles).
With fully Charged defy,
Power down defy, and with Volume+ held, press power key (shows "BootLoader 9.10, Battery OK etc").
Run RSD Lite, v5.6.
Select The .gz file in RSD Lite Filename box, will ask "It may take a while to uncompress, Continue ?",
Select "Uncompress Only" (it will be done, you could have used Winzip or Winrar to extract yourself instead, and chose the extracted sbf).
Connect Defy to USB, it should show "Connected" status in RSD Lite.
Click on the "Connected" line of text to reveal a little more info.
Click "Start", defy will show "SW Update in Progress".
Eventually (after several minutes) RSD will show "Phone[0000]: Phone is being rebooted".
Unfortunately, after some time it looked to RSD as if phone was not rebooting, and suggested Reboot manually.
This I tried multiple times but was in boot loop with MotoBlur animation and eventually black screen and repeating.
I pulled battery, reinsterted battery and attempted manual boot again, no joy, boot looping.
I pulled battery, holding volume down, and power on, and triangle with Exclamation mark (!).
I tapped repeatedly on bottom RHS corner of display and got the "Android System Recovery (2e)"
(some people say to hold down both volume up and down simultaneously, but my works best with bottom RHS corner taps).
Ignore the "E:Can't Open /cache/recovery/command" in yellow on bottom of display.
Select "Wipe Data/Factory Reset", tap OK on bottom left hand side of display (power button does nothing for me within
the system recovery).
After Factory wipe, select "Wipe Cache partition", and tap OK again.
Select "Reboot system now", and OK again.
We were back in business with a properley booting Eclair 2.1-update1 (was a bit tense for a while)
(Perhaps I should have done factory reset, cache wipe before RSD lite flashing).
In new flashed Eclair,
Settings/Sound & Display, select "Screen Timeout"=10 minutes.
Settings/Applications, tick "Unknown Sources".
Settings/Applications/Development, tick "USB Debugging".
File Manager app, I selected Framearoot v1.5.2 (others were tried but caused problems).
Choose "Install SuperUser" (NOT "Install SuperSu").
Hit "Gimli" exploit text, should show "Success", Reboot just for the hell of it.
File Manager, Install, SndInitDefy v1.4, and click "Install 2ndInit Recovery" button. (tried others, only this version worked for me)
SuperUser will pop up twice asking to Allow 2ndInit root premissions, grant the request each time.
Light will turn Green. (And read instructions).
Settings/Applications/Development, UN-TICK "USB Debugging", ie turn it OFF.
Reboot, it will auto jump into Custom recovery when Blue light comes on (dont press anything to get there).
With "Boot" selected, press Power key.
With "Set Default" selected, press Power key.
Move cursor up to "2nd boot" selected,, press Power key.
"Go Back", selected,, press Power key.
"Reboot system", selected,, press Power key.
Let it Reboot without pressing Volume-down when blue light comes on, and then reboot again a second time, for good measure
One last time, roboot, but this time when Blue light comes on press Volumn-down botton, and there you are custom recovery.
You will see "Android Bootmenu (v0.6.1)".
I originally had problems trying to "Install zip from SDCard", as it could not find the sdcard, I eventually figured out
that maybe because I had deleted sdcard stuff from previous android installation and that it did not like it.
So, I copied my stuff from sdcard to hard drive, and within settings/storage, formatted sdcard, after that I had no
problems at all. (just a lot of files to copy back to newly formatted sdcard).
Everything hunky dory.
EDIT:
ALL software mentioned above was present on XDA at time of writing, lots of defy links are broken here.
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.
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