Database Info

Milestone 2 Firmware

hello,
during the restore with clockworthmod recovery, the phone hangs up.
now is the system damage and no boot the phone. bootloader and menu for hard-reset(X+power works).
i need a sbf file for the european milestone 2 with motoa953 chipset for flashing with rsd lite.
gives a update.zip for the sdcard with clockworthmod revory to start from the menu "apply sdcard update.zip) with verifying
many thanks

try data wipe/factory reset and wipe cache in the clockwork or stock recovery..might fix the problem.
Sent from my DROID2 using XDA App

this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(

Rennert said:
this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(
Click to expand...
Click to collapse
Look on the forums and see how to sbf, that should fix the problem. And if not, you "bricked" it..if you can get into the stock recovery by holding the x button down and it comes up and what not then its salvageable but if all you get is the motorola m then it might be toast. Give sbf'ing a try.
Edit: Sorry I didn't really read your original post, sorry, you know how to sbf but don't have the file..I couldn't tell you where to get that...go to androidforums.com or droidlife.com and maybe someone can help over there because obviously im the only one responding...
Sent from my DROID2 using XDA App

The problem is, the milestone 2 have another chipset (a953) like droid2. Rsd lite says: firmware is not compatible with this phone. On recovery mode with update.zip can i only flash original firmware (verifization).
Today i go in the vodafone shop, the phone is only 1 week old.
Can i create a working sbf file from my clockworthmod* .img? I have many complete backups on my sdcard.
Or how can i make a sbf file from the system of another milestone 2. This would i flash into my ms2 with rsdlite
Sent from my Milestone using XDA App

http://www.mydroidworld.com/forums/android-hacks/1207-milestone-sbf-files.html
Stumbled apon this but im not sure if this is for the milestone 1 or 2...
Sent from my DROID2 using XDA App

@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.

I stumbled on this one (similar) to the one above when looking up bootstrapping the Milestone 2
hXXp://and-developers.com/sbf:milestone2
Dunno if it helps (sorry as I'm a lurker I have to HXXP).

dogei22 said:
@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.
Click to expand...
Click to collapse
With Droid X/2 recovery Bootstrap you can install ClockworkMod v2.5.0.8.
Edit: Please read instructions before you try the application.

Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.

dogei22 said:
Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.
Click to expand...
Click to collapse
For now only backup just in case.
I am doing some tests and hoping that if something goes wrong I can restore my phone with that backup.
Edit: Droid Overclock can be useful for example to change some Build Props(Dalvik VM, Max EVTs, etc)
Sent from my MotoA953 using Tapatalk

Try it, appear the original european firmware.
http://modmymobile.com/forums/593-m...558715-milestone-2-firmwares-superthread.html
Tell us if everything is ok.

[Q] [help]wifi doesn't work after unbrick D2G

hi, my d2g was brick, i m already solve the problem (thx to the develop made happed) and work perfect but just the wifi stay connecting... and dont wanna work
i was trying with 5 different routers with different method (WEP WAP... on/off, reset, etc...) but doesn't work yet :s
any idea???? what's the problem???
thank you in advantage
ps: i know of others user with d2g had the same problem after unbrick their phone.

done
i could solve the problem of wifi, now i got another one, is the Airplane Mode stay turning on and off with out stop!!!!

fulvi0 said:
i could solve the problem of wifi, now i got another one, is the Airplane Mode stay turning on and off with out stop!!!!
Click to expand...
Click to collapse
Flash unbrick sbf again and wipe before update to 629
Sent from my DROID2 GLOBAL using xda premium

Thx u. I just wipe. (Hard restore ) i working good
Sent from my DROID2 GLOBAL using xda premium

I can't wipe in recovery I can't see options

when you see android guy with! , press both volume buttons
Sent from my DROID X2 using xda premium

I try wipe and nothing change wifi not working

roxsy said:
I try wipe and nothing change wifi not working
Click to expand...
Click to collapse
Did you do all the steps (applying the update as well)? Does the system show as 2.3.4?

yea 2,3,4 but I can't Root by superoneclick and pete's motorola root tool

roxsy said:
yea 2,3,4 but I can't Root by superoneclick and pete's motorola root tool
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1592154
Sent from my DROID2 GLOBAL using xda premium

hi, i got same problem, can you help me?
i just only unbrick and unlock band to use AT&T network
and now wifi can search but cant connect...!

Your phone was on 4.5.629 or you flashed it to 4.5.629 during the unbrick/rooting process.
You did not update to 4.5.629 after that.
This issue manifests on devices that were updated to 4.5.629 (Android 2.3.4) and then were left on 4.5.608 after the unbrick & rooting process.

1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf)
2. Flash Repack_629 SBF using RSDLite (BL=2 BOOT REC CDTf__Repack_629.sbf)
3. Reboot, wipe data and cache
4. Enable Unknown Source and Development features in Setting
5. Root D2G with SuperOneClick v2.3.3
6. Install OtaRootKeeper, Run Protect-root then temp-unroot
7. Reboot to recovery then install 629 OTA update.zip then reboot(Blur_Version.4.5.608.A956.Verizon.en.US.zip)
8. Open OtaRootKeeper and restore Root
9. Install Droid 2 Recovery Bootstap.apkthen Reboot to Recovery
10. At Clockwork Recovery, run Backup the nan-droid
11. Flash 330 SBF suing RSDLite (VRZ_A956_2.4.33_1FF_01.sbf) --> After flash completed, phone will BRICKED, don’t worry
12. Flash 608 using EzSBF on USB stick (1KDStaz_D2G_4.5.608.iso) --> After flash completed, phone will BRICKED, don’t worry
13. Flash Repack_629 SBF using RSDLite (2_BL=2 BOOT REC CDTf__Repack_629.sbf)
14. Reboot, wipe data and cache
15. Enable Unknown source and Development features in Setting
16. Root D2G with SuperOneClick v2.3.3
17. Install Droid 2 Recovery Bootstap.apk then Reboot to Recovery
18. At Clockwork Recovery, Wipe Cache and install band unlock (TBH_Band_Unlock_v2.0.zip)
19. At Clockwork Recovery, run RESTORE the nan-droid (the one that backup on step 10)
20. Reboot phone then it should be able to us AT&T, T-Mobile and Verizon and enjoy
Click to expand...
Click to collapse
i do like this. pls help me!!!
i use AT&T network

wipe data again

i try third times but nothing happen ! wipe cache, data....

If you followed the instructions above, did you restore a nandroid backup of .608, or a nandroid backup of .629? Originally you said you were on .608, so if you made a nandroid backup of that, and restored it, you would be experiencing the issue you mention.

Hi,i have the same issue,at first when bootloader was accepting downgrade i could go on froyo where wifi worked perfect,but on neither GB release wifi just have turning on/turning off disease,tried every possible thing but nothing is working except MIUI.us but its CDMA rom and i'm gsm user.according to this its something with firmware related in my case.

Problem with Clockwork Recovery

Hello, I have a Droid 2 Global, with OTA .629, but already rooted and everything, but i have constant reboots since i had the phone (with .330, .607, .608 and .629) maybe its a defective phone, i dont know really, but the problem i have actually it is:
I installed the newest clockwork recovery using Rom Manager, but the recovery it doesnt do anything, it says it wipe data/cache, and very quickly, but it doesnt, it gives me error formating /system, etc...
It says that installed sucessfully Cyanogenmod 7.2 (latest nightly) but, it freezes at M logo... what should i do?

stop using rom manager
use a different cwm version
Sent from my DROID X2 using xda premium

suggestions?

try droid 2 bootstrap
or you already have rom manager, you can get different cwm versions, with that
try last version that worked for you

This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.

projektorboy said:
This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.
Click to expand...
Click to collapse
thank you, it worked... i used d2g recovery cmw, and didnt work...

projektorboy said:
This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.
Click to expand...
Click to collapse
that's because Rom Manager isn't recommended
I used Droid 2 bootstrap, with 2.4.33 and 4.5.608 and it worked fine
i used d2g recovery cmw, and didnt work...
Click to expand...
Click to collapse
your cwm was likely corrupt, selecting Droid x just installed a complete cwm
edit: if you are using rom manager you have to use Droid X 2nd Init, or just use Droid 2 bootstrap

sd_shadow said:
that's because Rom Manager isn't recommended
I used Droid 2 bootstrap, with 2.4.33 and 4.5.608 and it worked fine
Click to expand...
Click to collapse
You aren't quite right.
The correct way is installing Droid 2 Bootstrap Recovery and using that to hijack. This will give you CWM 2.0.0.x. Once done, install the Droid X (2nd init) CWM via ROM Manager, and you'll end up with a fully functional CWM 5.0.0.x.
(Custom ROMs like CM7, CM9, and MIUI come with 5.0.0.x preinstalled, and restoring a backup made with 5.0.0.x is impossible if running 2.0.0.x.)

ok, i dont really get it...
using Droid X 2nd-init, it wipes and everything, and flashes CM9-D2G-04162012 and update-cm-7-20120420-NIGHTLY-droid2we-signed, coming from stock .629 firmware, and it freezes at M logo after rebooting, then is necessary sbf'ing again .608, and unbrick it againg, and is a loooong process....

again there are no roms built for .629, so you need to search for ones that are reported to work, and how they got them to work

In general, according to people who use CM9 on top of .629, any .608 ROM works on .629. There are no differences.

joel_sinbad said:
ok, i dont really get it...
using Droid X 2nd-init, it wipes and everything, and flashes CM9-D2G-04162012 and update-cm-7-20120420-NIGHTLY-droid2we-signed, coming from stock .629 firmware, and it freezes at M logo after rebooting, then is necessary sbf'ing again .608, and unbrick it againg, and is a loooong process....
Click to expand...
Click to collapse
have you tried, wiping cache/data, after flashing

not for me, used latest CM9 and CM7 nightlies, freezes at M logo... only before flashing update.zip for getting from .608 (hybrid?) to .629... custom roms work somewhat ok, without wi-fi, Sound Settings fc, and other little details...
sd_shadow said:
have you tried, wiping cache/data, after flashing
Click to expand...
Click to collapse
yeah, after, and before... no sucess

sd_shadow said:
have you tried, wiping cache/data, after flashing
Click to expand...
Click to collapse
yeah, after, and before... no sucess

you could try
1-wipe data,cache,davlick
2-mount and format system
3-mount system and install zip

done, no results...

I get the same results after flashing MIUI over .629. It flashes ok using Droid X(2-int) recovery but after that its bugy as hell. I cant switch to GSM, tried dialing 46xx number and using network toggle. GSM doesn't see to work at all and when i try to restore my old rom it gets stuck on M logo.

Transceiver issues are in no way related to CWM.

It would be nice if someone who is on .629 can confirm that GSM works on CM7,9 MIUI or any other room. I want some ICS goodness but it looks like it would be just a waste of time flashing again.

Well, .629 doesn't really differ from .608 if you're looking at it from a custom ROM's point of view. Same kernel and modules, and that's all a custom ROM needs from the “base” system.

[Q] Stuck asus logo on TF300T Firmware 10.4.2.18

Hello.
A was installed a recovery on my tablet ( CWM ) and rooted.
Then i wipe all ( data/factory reset, cache, dalvik cache ) and the i was install cm10.1
Now my tablet are stuck on asus logo and i cannot do anything.
My firmware is 10.4.2.18 ( i was updated then a was rooted my tablet )
What can i do?
Sorry my english.
Thank you.

Please someone.
Nobody?
My tablet is on from yesterday because if i turn off she turn on
Sent from my LG-P500 using xda app-developers app

READ COMPLETELY BEFORE ATTEMPTING!
While the tablet is on, hold power down until it turns off. As soon as it turns off press volume down while still holding the power button. That will enable you to choose to go back into your recovery or fastboot. Recovery will be the icon labeled RCK and fast boot will be the USB icon.
You could also choose to just enter RCK (recovery) and try to do a factory reset, try to flash the ROM again or flash another ROM from your SD card.
If you are positive you have choosen and flashed the correct ROM the first time, did you remember to do a factory reset, clear cache and dalvik before flashing the ROM? That could very well be the reason you are in a boot loop.
If you are using CWM as your recovery and cannot use it to flash a new ROM from your SD card, you may need to flash TWRP using fast boot in order to flash a different ROM from your SD card.
There is a TWRP thread in the development section. Download the TWRP recovery blob and flash it using fast boot.
You also have another option. You can choose to flash back to stock using fastboot. Here is a great tutorial that will guide you step by step on how to do it. If you are unsure of what to do and want a quick fix, use this. Make sure to thank him for the great tutorial after you finish if you decide to go this route.
http://forum.xda-developers.com/showthread.php?p=35805045
Good luck
Sent from my LG-LG855 using Xparent Green Tapatalk 2

Hello.
Yes, i was sellected factory reset first ( wipe data / factory reset ).
I have jellybro and cm10.1 on my sdcard. I wipped all more times and try to install roms, but the result was same.
In this case, shoud it by solve it in the same way?
Sent from my LG-P500 using xda app-developers app

I had this problem with mine when I was flashing it, but I was still on the ICS firmware when I tried to flash CM10, that's what caused the problem since the boot partition gets resized in the stock JB update.
Are you sure you were on a 4.1 OTA stock update before you tried this? Have you tried wiping data/system/cache and re-flashing the ROM again?
I ran a backup of my stock rom before flashing CM10, so when it wouldn't boot after the initial flash, I restored, and it was then stuck at the ASUS screen saying 'unlocked device' what I had to do to mine was extract boot.blob from cm9.1, boot the tablet into fastboot, and then run fastboot -i 0x0B05 flash boot boot.blob that got me booted back into a live tablet. I then took the JB OTA, and started over, flashing recovery, root, doing another backup, and then wiping and flashing CM10, which worked perfectly.
HOWEVER. If you're 100% certain you were on JB already, this may not be the case.

Yes. I was on jb 4.1.1, kernel 3.1 ( i,m not sure, but this i remember ) and, for sure, firmware 10.4.2.18
Sent from my LG-P500 using xda app-developers app

I would use the link I posted above. It will at least get you back to stock. It's a very easy tutorial to follow. Once you get the tablet where it will boot, then you can decide on another ROM.
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2

I wanna thank you...
It works now... the is you very much
Sent from my Transformer Pad TF300T using Xparent Blue Tapatalk 2

slackware87 said:
I wanna thank you...
It works now... the is you very much
Sent from my Transformer Pad TF300T using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
AWESOME! Glad it worked for you.
Sent from my LG-LG855 using Xparent Green Tapatalk 2

[Q] Help needed: Softbrick while using Bootstrap to flash ROM

Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.

kenlohwj said:
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
Click to expand...
Click to collapse
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.

-edited-

turffe said:
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
Click to expand...
Click to collapse
thank you so much for the prompt reply. So my location is in Malaysia>South East Asia, and it should be MB865. Do i use the 'Android 4.0.4
Blur_Version.67.220.3.ME865.Retail.en.05' file to fxz it? found from the sbf developer site
My previous OTA was 4.0.4, i was worried that if i used it on the earlier custom ROM 4.2.2 that i had, i will hard brick it. So will there be any cause for concern?
and what do they do with the .xml file in the file prior to fxz it? is it fine if i skip that step?

On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk

turffe said:
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
Click to expand...
Click to collapse
MB865, therefore i suppose it should be Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03. Unfortunately I had sent the phone to a repair guy, so no chance for me to try it out yet. Will update you tomorrow!

that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit

kenlohwj said:
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
Click to expand...
Click to collapse
I'm glad you got it figured out. :thumbup: