Database Users

My Droid 2 Global got Stuck on M logo

This is my bad day . My Droid 2 Global got stuck on M logo when I tried to root and install the new ROM . I have tried alot of SBF from the Droid 2 but it's seem nothing fix my phone. So, anyone can help me with the new SBF for Droid 2 Global

Which SBF did you use? I'm not aware of one being released for the D2G and using the one for the D2 will certainly screw up your phone.

There isn't a SBF for the D2G yet. You should have waited for it before trying anything like this.

If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.

I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.

hamabucon said:
I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.
Click to expand...
Click to collapse
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.

newk8600 said:
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.
Click to expand...
Click to collapse
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047

hamabucon said:
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047
Click to expand...
Click to collapse
Did you make a backup with koush's bootstrapped clockwork recovery? if so you should try and restore it. otherwise you might be out of luck until the sbf drops.

Maybe I'm out of Luck . But is there a chance to update the new ROM using the stock Recovery ? . I saw there are the option apply: update.zip

It will only work if you have the rom signed with moto's keys or it won't get through. That's why we use koush's bootstrapped clockwork. Because it doesn't have signature verification. Well it does but we can toggle it off.
Sent from my DROID2 using XDA App

Can you estimate when the SBF for D2 G release ?

newk8600 said:
If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.
Click to expand...
Click to collapse
I have the same problem with the droid 2, except i mistakenly flashed with the droid 2 global without really thinking about it. I'm stuck at the M logo, and i've tried doing all of the above but i cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?

I remembered that i install the stock ROm deodexed for Droid 2 Global . But why my phone bricked ? Is that the problem from my phone?

dotmike said:
I cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?
Click to expand...
Click to collapse
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App

I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?

newk8600 said:
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk

hamabucon said:
I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?
Click to expand...
Click to collapse
You could try, but you need to get into cw recovery on the broken one first...
Sent from my Milestone using Tapatalk

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App

, Still wait for my little hopeness

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
newk8600 said:
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes, apologies for taking over a thread with my question, however to newk8600, I didn't know that holding the up key on the keyboard booted into the bootloader! I managed to sbf from there since RSDLite read the phone then.
Apologies for any confusion, and thank you again for the help.

motorola droid 2 bricked need help

i have Motorola droid 2 on 2.2 rooted with bootstrap recovery, everything was workin fine till i decided to install custom rom, which was unleashed epic 2.5 (by mat) and now everytime i turn on my phone it goes into a loop reboots and never turns on all the way.
i have tried using sbf RSDlite to restore it, tried using linux ubuntu(newk8600 method ty btw) method as well to restore it, none seems to work i keep getting errors whenever i try to do it.
however before i installed the custom rom i did full backup using bootstrap recovery but the only way (that i know) to get in recovery is using bootstrap app, so is there a way i can manually get into bootstrap recovery so i can restore from backup?
please let me know, or if you have different method i'll appreciate your help. thanks in advance.

Which version of the software did you have before you installed epic unleashed, and which SBF did you use?
From what I have heard, Epic Unleashed will "brick" your phone if you try to install it on the 2.3.20 build. Since your phone did get bricked, it's likely that you are running 2.3.20 and not 2.2. You might want to make sure you are using the 2.3.20 SBF to flash your phone, and not the 2.2 SBF (which won't work because the kernel changed between the two)...

What type of errors do you get?

i always have luck getting into clockwork recovery by having my phone plugged in and within the first few seconds taking out my battery forcing it to take along time booting after the M logo and hence putting it into clockwork. I hope this helps

after you get passed the M pull the battery then boot back up it should come up in to recovery

thank you all for your help, however i tried all of these steps already, but i found another way to get it workin, here is the solution to whom got the same problem as mine.
its not letting me post the link for some reason, anyway just search for (Droid 2 Global SBF File (2.4.29) Full and RSDLite ).
just got relased today , big thanks to team Black Hat and MyDroidWorld
hope that helps.

Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App

orkillakilla said:
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.

Phoible said:
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Click to expand...
Click to collapse
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App

orkillakilla said:
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It's all good people need to read where they are posting this is in the D2 General section not the D2 Global general section. That's half his problem, he's been looking at ROMs for the original D2 not the device that he currently uses.

Buddies droid x easiest way to root n install custom rom?

Looking to just one click and install a stable rom(cm7?) on my buddies droid x.. any of u guys know of a one click for droid x and the best available rom for droid x.. I'm not looking for fanboy roms here just want the best all around average user experience.
sent from my cm7speedy /or/ miuispeedy

noskoviak said:
Looking to just one click and install a stable rom(cm7?) on my buddies droid x.. any of u guys know of a one click for droid x and the best available rom for droid x.. I'm not looking for fanboy roms here just want the best all around average user experience.
sent from my cm7speedy /or/ miuispeedy
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=File:Motorola_Droid_X.png
Check out that sticky. Has all the information you need. Hard to give an opinion without being a fanboy, so just read on up and decide for yourself. BTW, cm7 is not very stable for the droid x, so you might want to look at alternatives.

Z4root in the link. I don't think you can install cm7 on the DX due to the locked bootloader.
http://www.DroidXForums.com/forum/droid-x-hacks/13259-z4root-download-links-get-your-root-here.html
Sent from my DROIDX

I would recommend liberty or apex rom, had them both before and really liked them. Currently running the team black hat .595 rooted and deodexed. I froze all the bloat, changed the boot logo and animation too. Probably just depends on what level of customization you are happy with.
DX 2.3.3

CM7 isn't available on the DX so you're SOL on that one.
The easiest way to root is (as previously mentioned) z4root which is all done on t he phone itself, you just need to grab the .apk from the XDA forums here.
Personally I would recommend Fission over Liberty but that is only because my DX doesn't seem to always play nice with some of the Liberty tweaks. Fission 2.6.1 (Froyo 2.2.1) hasn't been updated in a while but it is very solid, very fast & has excellent battery life (when paired with SetCPU.)
If you want to go the *leaked* (meaning it isn't done yet) Gingerbread route, there is the TBH (TeamBlackHat) stock releases or you can also check out Liberty Gingerbread (which I've been running for the past couple of days). So far so good with Liberty GB but battery wise I think its better on something like Fission.

marculous said:
I would recommend liberty or apex rom, had them both before and really liked them. Currently running the team black hat .595 rooted and deodexed. I froze all the bloat, changed the boot logo and animation too. Probably just depends on what level of customization you are happy with.
DX 2.3.3
Click to expand...
Click to collapse
Did u ever get root permisions to work on titanium backup and how?... Root is workin for things like root explorer addfree amd bootstrap but I cant get root permisions on titaniumbackup?
Sent from my DROIDX using XDA App

owenbeals said:
Did u ever get root permisions to work on titanium backup and how?... Root is workin for things like root explorer addfree amd bootstrap but I cant get root permisions on titaniumbackup?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Nevermind I figured it out apparently .595 is missing busybox... Just had to dl it from market
Sent from my DROIDX using XDA App

Gingerbreak 1.20 also roots unroots which is what I thought was needed for the .595?

Nope the deodexed .595 was rooted but was missing busybox
Sent from my DROIDX using XDA App

I've taken a quick dip into GummyJar...
Apex...
And have stuck with Liberty ever since switching to it.
Currently running liberty gingerbread 0.5 actually...and even as a beta it seems to be running flawlessly.
2.01 is on froyo, and is a stable version if you'd prefer that.

LB 2.0.1
Liberty 2.0.1 is the best user experience. Plus they have a supported and free toolbox. Z4 root works.

Ok, so I have a question for u guys if u don’t mind. My buddy has a droid x that he is wanting to flash custom roms on. I have a htc evo and I have quite a bit of experience when it comes to that phone but im completely clue less when it comes to the droid x. He has ran z 4 root and is fully rooted and has a custom recovery but he was saying something about he needed to deodex the files on his phone before he can flash a custom rom which sounds weird to me. If any one could help me help him I and he would greatly appreciate it. Thanks.
Sent from my PC36100 using XDA Premium App

Tiffany84 said:
Ok, so I have a question for u guys if u don’t mind. My buddy has a droid x that he is wanting to flash custom roms on. I have a htc evo and I have quite a bit of experience when it comes to that phone but im completely clue less when it comes to the droid x. He has ran z 4 root and is fully rooted and has a custom recovery but he was saying something about he needed to deodex the files on his phone before he can flash a custom rom which sounds weird to me. If any one could help me help him I and he would greatly appreciate it. Thanks.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
That is wrong actually...you'd only need to do that if he wanted to keep the stock ROM & just theme it. If he wants to flash a different ROM then all you'd have to do is drop the ZIP file onto the root location of the SD card & wipe cache, wipe data, wipe Dalvik and then install the ROM (like you would on any other ROM via CWM.)

JagoX said:
That is wrong actually...you'd only need to do that if he wanted to keep the stock ROM & just theme it. If he wants to flash a different ROM then all you'd have to do is drop the ZIP file onto the root location of the SD card & wipe cache, wipe data, wipe Dalvik and then install the ROM (like you would on any other ROM via CWM.)
Click to expand...
Click to collapse
Exactly. That's what I was thinking. I tried telling him that the stock rom would have to be deodexed in order to flash a theme but since he was fully rooted and he had a custom recovery he should be able to flash a rom but he wasn't listening. So thank u so much for responding. I really appreciate it. I guess since im a chick he thinks I don't know what im talking about. Thanks again.
Sent from my PC36100 using XDA Premium App

Tiffany84 said:
Exactly. That's what I was thinking. I tried telling him that the stock rom would have to be deodexed in order to flash a theme but since he was fully rooted and he had a custom recovery he should be able to flash a rom but he wasn't listening. So thank u so much for responding. I really appreciate it. I guess since im a chick he thinks I don't know what im talking about. Thanks again.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Maybe you should keep him at stock and unrooted for punishment lol

Ditto.
sent from my cm7speedy /or/ miuispeedy

Thanks for all the responses guys and girl... very impressed with the support....so
cm7/miui is a no = bummer....
Fission = most stable (its at 2.2 still right?)
Liberty = most promising GB rom?
Does CWM work for the DX my buddy kept telling me he read somewhere it doesn't. Also does that fission rom flash its own recovery?
sent from my cm7speedy /or/ miuispeedy

noskoviak said:
Thanks for all the responses guys and girl... very impressed with the support....so
cm7/miui is a no = bummer....
Fission = most stable (its at 2.2 still right?)
Liberty = most promising GB rom?
Does CWM work for the DX my buddy kept telling me he read somewhere it doesn't. Also does that fission rom flash its own recovery?
sent from my cm7speedy /or/ miuispeedy
Click to expand...
Click to collapse
Fission is indeed 2.2 (2.2.1 to be exact) and (on my phone) it works fantastic...Liberty and a few others aren't as friendly some apparent reason.
Liberty is the most active I would say but b/c they do a lot of tweaks, some phones (like mine) are finicky with those tweaks. Their Froyo release (2.0.1) is solid & their (leaked) GB mod isn't half bad either.
CWM does work, you just have to apply the Droid X Bootstrap Recovery installed & run the bootstrap in the app then reboot in order to get to the CWM interface.

So that cwm business sounds annoying do I have to do that everytime? Is there a working recovery for this phone such as amon ra? As I mentioned before fission includes one correct? Can the fission recovery be used to flash other roms? Also is there a 2.3 update coming for fission?
sent from my cm7speedy /or/ miuispeedy

noskoviak said:
So that cwm business sounds annoying do I have to do that everytime? Is there a working recovery for this phone such as amon ra? As I mentioned before fission includes one correct? Can the fission recovery be used to flash other roms? Also is there a 2.3 update coming for fission?
sent from my cm7speedy /or/ miuispeedy
Click to expand...
Click to collapse
It's not as bad as it sounds to honest, it takes just as long on my wife's Dinc (running CM7.0.3) to hold down power, choose reboot then choose recovery to get into CWM. The bootstrap app is free (just gotta search online) or you can support Koush (the dev) by buying it in the Android Market ($2.00).
That's the best the Droid X can do to get into CWM b/c of Motorola locking down the bootloader. The only ROM I know of that lets you boot into recovery is Liberty *BUT* it honestly is faster using the dedicated bootstrap app.
Not sure about Fission going to 2.3 however not much has been updated on Fission since 2.6.1 (based on 2.2.1) was released but my guess is that it would however get updated to Gingerbread. GB on the DX is not *officially* out yet so all the leaks at this point are still just leaks...and all the GB-based ROMs are based on potentially unfinished leaks. It does run (really) well but it still is running a handful of Motorola services (even Liberty GB is) and I prefer as close to AOSP as possible...which is why I always go back to Fission 2.6.1.
Seeing 60-75MB of memory used (instead of 100+MB) in "running services" with (near) AOSP ROMs makes my inner OCD geek happy

[Q] Rom Manager on rooted .596 problem

I am having issues using Rom Manager (v4.3.2.4, should be lateset) on my rooted DroidX running .596 from TBH. Now I know I had to use the Droid2 bootstrapper to apply the TBH update, but I can't seem to get the ClockworkMod Recovery to work now that I have updated. I've tried both the Droid X and Droid 2 versions. It says it downloads, then when I try to reboot into recovery it just boots up as normal.
I know I am probably missing something pretty obvious but as I am new to the Rom portion of root I apologize in advance.

havetolovemusic said:
I am having issues using Rom Manager (v4.3.2.4, should be lateset) on my rooted DroidX running .596 from TBH. Now I know I had to use the Droid2 bootstrapper to apply the TBH update, but I can't seem to get the ClockworkMod Recovery to work now that I have updated. I've tried both the Droid X and Droid 2 versions. It says it downloads, then when I try to reboot into recovery it just boots up as normal.
I know I am probably missing something pretty obvious but as I am new to the Rom portion of root I apologize in advance.
Click to expand...
Click to collapse
This is probably a dumb question but did you apply the rooted version or the non rooted?
Sent from my DROIDX using XDA App

I applied the rooted version. All the root is fine, it has been granted superuser permissions.

havetolovemusic said:
I applied the rooted version. All the root is fine, it has been granted superuser permissions.
Click to expand...
Click to collapse
That's weird!
Sent from my DROIDX using XDA App

bootstrap to have cwm as permanent recovery

can i bootstrap to the custom recovery and then flash cwm as my primary recovery w/ out the boot strap !

You can only flash Motorola stock update.zip's in stock recovery.
Sent from my EncounterICS droid 2

Ok thank I was trying to get a perm recovery so I'm guess the locked bootloaders have something to do w that !
Thanks for your answer!
Sent from my DROID2 using XDA App

Damn locked bootloader. No problem.
Sent from my EncounterICS droid 2

ghostv7142 said:
Ok thank I was trying to get a perm recovery so I'm guess the locked bootloaders have something to do w that !
Thanks for your answer!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
The locked bootloaders have everything to do with that, unfortunately. They also keep us from having custom kernels on D2/D2g/DX along with almost every other Motorola device.
Even my coffee pot has a cutom kernel, why can't Moto let me put one on my phone??!!

I thought they were unlocking them already hmm that sucks a perm custom recovery would be nice I don't like the bootsrapping at all I feel a cr would make me feel better ! Specialy when flashing beta roms