Database Users

[Q] Is Rom Manager working for Droid 2?

Not sure if this is a frequently asked question, but is Rom Manager working for the Droid 2? Matt's section give an error, and the rest either don't work or are not important at all. Is there anyway to fix this or is there a better app? Thanks.

HerroMoto said:
Not sure if this is a frequently asked question, but is Rom Manager working for the Droid 2? Matt's section give an error, and the rest either don't work or are not important at all. Is there anyway to fix this or is there a better app? Thanks.
Click to expand...
Click to collapse
Yeah it works. It allows you to install a newer superuser, manage backups, boot into recovery, install a new recovery if one becomes available etc. Matt's section I don't think is completely setup. When the bootloader gets cracked, I think this will be more useful with more roms available.
Sent from my DROID2 using Tapatalk

Sorry I should have rephrased my question. I know everything works on it, but it doesn't have any roms on it. It just has the 2 superuser things to download on it and then it has 2 other sections that are empty. I just thought it would be up and running perfect by now.

Yeah, but there aren't any real roms. The so called roms that are out just replace system stuff, they aren't really full roms. If/when the bootloader is cracked, we will eventually get support for big name roms, and those will pop up in rom manager.
Companies are cracking down on modders; I don't know why. We are like 1% of the users. As long as this bootloader continues to stand in our way, rom manager is going to be pretty empty.

ROM Manger question? D2G
when I run Backup Current ROM on Motorola droid 2 global my phone reboot. it seems that it is not working.
can someone help please
thanks

mhansaq said:
when I run Backup Current ROM on Motorola droid 2 global my phone reboot. it seems that it is not working.
can someone help please
thanks
Click to expand...
Click to collapse
Have you ran koush's bootstrap before you installed rom manager? and I'm not sure if backup via ROM manager works on the D2 or D2g but I've never used ROM manager. Koush's bootstrap does everything so I don't see the point of another program but that's just my opinion.

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.

[Q] NEED HELP. DROID X Bootstrapper. Sending a phone back to VERIZON. Desperate

First i'm going to say sorry as i know this isn't the first and probably won't be the last thread posted about removing droid X bootstrapper. With that said thank you in advance for helping me.
Before i go on i'll preface by saying i am no expert but with proper instruction i can learn very easily. I rooted my DX using z4root and used droid x bootstrapper to create a nandroid and flashed the Fission Rom. I am new to the DX, came from the DINC, and the only reason i rooted was because my phone was rebooting randomly and i thought maybe that would fix it but it didn't so i was able to get a refurb DX which is working better already and so now i have to send my old back to Verizon. Problem is i unrooted it and restored to defaults and Bootstrapper, Terminal Emulator, and SU were all still there. so i researched the boards since this community has made me excited to be an android user, and tried both methods of Root explorer and Terminal emulator, and even flashed maderstcock340.zip but again upon restoring to defaults, all 3 apps showed up again.
I need help, i didn't want to ask for help because i dont want to bother anyone but i need the help. Even a link to something else that i should try would be a great help.
I mean even if anyone is willing to skype with me and help me out that way i'll buy you a 6 pack.
EDIT: Will using the .340 system only sbf work to remove it? and if not will using TBH's 2.3.32 fix it??!?!

Have you tried unrooting with z4, you can uninstall the other two in the market. If z4 fails to unroot, you might have to flash a sbf. Its easy find " how to's" in the forums.
Sent from my DROIDX using XDA App

thecontrolm7cl said:
First i'm going to say sorry as i know this isn't the first and probably won't be the last thread posted about removing droid X bootstrapper. With that said thank you in advance for helping me.
Before i go on i'll preface by saying i am no expert but with proper instruction i can learn very easily. I rooted my DX using z4root and used droid x bootstrapper to create a nandroid and flashed the Fission Rom. I am new to the DX, came from the DINC, and the only reason i rooted was because my phone was rebooting randomly and i thought maybe that would fix it but it didn't so i was able to get a refurb DX which is working better already and so now i have to send my old back to Verizon. Problem is i unrooted it and restored to defaults and Bootstrapper, Terminal Emulator, and SU were all still there. so i researched the boards since this community has made me excited to be an android user, and tried both methods of Root explorer and Terminal emulator, and even flashed maderstcock340.zip but again upon restoring to defaults, all 3 apps showed up again.
I need help, i didn't want to ask for help because i dont want to bother anyone but i need the help. Even a link to something else that i should try would be a great help.
I mean even if anyone is willing to skype with me and help me out that way i'll buy you a 6 pack.
Click to expand...
Click to collapse
Have you tried sbf'ing?
Sent from my DROIDX using XDA App

bigshotrob22 said:
Have you tried sbf'ing?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well i thought that is what maderstcoks340.zip was supposed to be. A flashable sbf? can you direct me to a link where i can download the .340 SBF and the right version of RSD Lite

I'm currently at work and on my phone...so you'll have to find the links yourself...
But flashing the .340 won't get you completely back to stock. You'll need to find a link to the .320 sbf...I think there is one on droid-life.com
Apply the 320 and then the 340.
340 sbfs are easy to find...but you'll obviously need that too.

Jubakuba said:
I'm currently at work and on my phone...so you'll have to find the links yourself...
But flashing the .340 won't get you completely back to stock. You'll need to find a link to the .320 sbf...I think there is one on droid-life.com
Apply the 320 and then the 340.
340 sbfs are easy to find...but you'll obviously need that too.
Click to expand...
Click to collapse
got it all taken care of! Really pretty fearless now that i sat down and learned to SBF the problem is i run mac so i'll need to use a friends PC if i ever need to SBF again. Anyway thanks for the help!

Go go www.drewgaren.com and click on the sbf and root tab..i used his instructions to sbf...
Sent from my DROIDX using XDA App

Droid Pro Stuck On Bootloader

My Driod Pro is stuck in bootloader. It was not rooted. It was completely stock for that past 1.5 years. I had it in my pocket and went to use it and it was on the bootloader screen. I took it to Verizon and they couldn't do anything so ended up upgrading to iPhone 4S but I still want to get my Droid Pro working again...
Any thoughts? I saw other models with the bootloader issue but am not sure if those solutions would work for the Droid Pro.
(hopefully I won't lose all my stuff on the Droid Pro)
Thanks in advance!

Can you post or type what the bootloader screen says?
P.S. why did you go with the iphone over another Android

Bootloader
03.0A
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
That's what they screen says.
Went with an iPhone to just consolidate and family and friends have iPhones.

If it was a Samsung you'd use Odin and flash a new rom on...
any moto experts care to give us a clue what should be used for this situation?

I was able to revive the phone!
Used RSD Lite and SBF files. Ran it. Restarted phone by pulling battery. Got the green Androind icon with yeallow exclamation so did a full factory wipe and the phone started up perfectly.
Took a few more hours of research and finding the SBF files but it worked.
Thanks.

Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")

jago25_98 said:
Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")
Click to expand...
Click to collapse
you must install droid 2 bootstrapper from market....
open the app click on bootstrap recovery, then reboot recovery...
You must have your phone rooted...

I was going to say your best bet would be to sbf it back to verizon default following my instructions here but ignoring the root part. Iphone? Really??
http://forum.xda-developers.com/showthread.php?t=1590489

jago25_98 said:
Which .sdf did you use? Because recovery-clockwork-2.5.0.1-sholes.sbf
from
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
isn't working for me
("phone is not compatible with multi-interface superfile")
Click to expand...
Click to collapse
I used DroidPro_2.26.20_FULL.sbf.zip from MyDroidWorld.

retrobot said:
Iphone? Really??
Click to expand...
Click to collapse
Returned the iPhone and back on DroidPro!

dubLeE said:
I used DroidPro_2.26.20_FULL.sbf.zip from MyDroidWorld.
Click to expand...
Click to collapse
Thanks bud! There's thankfully a few mirrors out there for it post megaupload now.
I managed to get CyanogenMod9 on it but that was by rooting and then doing the .zip over the top.
But this wouldn't be as thourgher as using a .sbf would it? I mean, the kernel is still old right?
It seems to be running quite well but one problem. When trying to use the keyboard the screen goes blank... how's that image for that kind of thing you reckon?
For anyone else reading this, CM9 ICS seems to work ok apart from that keyboard problem, but I'm running an older kernel.
Can I achieve the same usability as a i9000 on Ice Cream Sandwich...?