Database Users

[Q] Stubborn Droid 2

To preface, I've been off the phone hacking/ROM flashing scene for a couple years now; previously working with Windows Mobile, so I know a lot has changed but I'm not largely unfamiliar with the general process of what we are doing here.
Droid 2 In Question:
System Version - Version.2.3.20.A955.Verizon.en.US (After OTA Update 03 NOV 10)
Baseband - BP_C_01.09.07P
I've got a stubborn Droid 2 that just WON'T boot to recovery. I bought a fresh Droid 2 last week, rooted via the 1-2-3 'One-Click' successfully. Then I attempted to follow AngDroid's Fission install step by step for my first ROM flash. http://forum.xda-developers.com/showthread.php?t=823473
Issues:
ROM Manager wouldn't do ANYTHING when I would select 'Reboot into Recovery' or attempting to select ROM using 'Install ROM from SD Card'.
Found and installed Koush's Bootstrapper, got 'SUCCESS!' pop-up when selected 'Bootstrap Recovery' yet when I tapped 'Reboot Recovery' nothing happened.
I then attempted to re-install the SBF (which I'm still not 100% clear on what the role of the SBF is, perhaps just the Baseband?) using both AngDroid's instructions in his Fission thread as well as using RSD Lite 4.7+patch AND 4.8 AND 4.9 instructions from this thread. http://forum.xda-developers.com/showthread.php?t=827624 All those attempts where unsuccessful. RSD wouldn't allow me to 'Start' the SBF flash which I can only assume is because I had the latest version on my Droid 2.
I then decided to restore my phone to factory and start over, so I booted the device pressing x, then search and selecting wipe data/factory reset. Once done, it rebooted and to my surprise it still had the Superuser Permissions app that was installed during the 1-2-3 One-Click process.
I went as far as to install the full Android SDK/Eclipse setup for ADB use and continued to run into 'operation not authorized', 'root not allowed on production ROMs' and 'failure' with any command attempting to remove SU Permissions app and install a diff. SU app/reboot into recovery.
I checked to see if I still, in fact, had SU permissions by re-installing Barnacle, it stated that it needed su but the Superuser Permissions app never prompt me to authorize su. There is also no way (that I see) to manually authorize su for barnacle, or any app, in the SU Permissions app.
Way Forward?
I believe that I either need to re-root and try to reboot to recovery again but I am not confident that will work.
I am starting to think that ROM Manager and Droid 2 Bootstrapper apps didn't have SU and might be why they didn't respond when I selected 'Reboot Recovery' options? As I stated I do not know how to manually authorize.
With this information, what am I to do from here?

That's strange. After root, you should be able to install SU from the market if the one click root doesn't already do it for you. When you run Koush's bootstrapper, the first time you should get a pop up from the SU program asking you if you want to allow or deny the bootstrapper. After that, everytime you load up the bootstrapper you should see a little pop up stating that it has been granted superuser privileges.
Try rooting again, this time use the 1 click root for 2.3.20 found here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html, and then go through the steps again and report back

Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?

wjones said:
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
Click to expand...
Click to collapse
Id wipe cache and wipe data/factory reset and start fresh. I've never had any of your problems and I think they can be fixxed with a factory reset.

Sounds like you didn't get rooted properly.
If it were me, I'd sbf and start over.
- Charge battery fully
- Get drivers from Motorola and install them (wait for it to finish)
- Get RSD 4.8+, and 2.3.20 sbf (make sure you get the full file)
- Wipe data and cache in stock recovery (access by power + X key, then search key)
- Boot into bootloader (power + Up key)
- Load RSD and make sure your device shows
- Choose the sbf and click Start
If you follow those steps exactly and sbf doesn't work, then you probably have a hardware problem either on your phone, your PC, or the USB cable.

karnovaran said:
Sounds like you didn't get rooted properly.
- Boot into bootloader (power + Up key)
Click to expand...
Click to collapse
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!

wjones said:
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
Click to expand...
Click to collapse
Yeah I don't know why some methods recommend PC Mode. Sbfs are meant to be flashed in bootloader.

Honestly, it sounds like everything is working like it should be, it's just some steps are being skipped or overlooked. Like the SBF in bootloader, and the sbf doesn't erase your data, you need to do a factory reset after sbfing so thats why your superuser app was still there.
There really is no such thing as a phone being stubborn, and majority of errors like that are from the user. Not to be insulting but thats just the case. The only time I have ever seen a stubborn piece of hardware is from overclocking, where some can go higher than others due to having a better piece of wafer. But if you rooted correctly, bootstrapped, etc, there is no reason that you wouldn't be able to install a ROM.

Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App

wjones said:
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is this solved now? May I close it?

Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App

wjones said:
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No problem! I'm in no rush to close it, was just curious Hope it all goes well

DONE!
It worked like a charm! Thanks for all the support!

wjones said:
It worked like a charm! Thanks for all the support!
Click to expand...
Click to collapse
Awesome. Could you add [SOLVED] to your thread title before the mods close it?

[Q] Getting to Clockworkmod Recovery the hard way

I have a rooted X stuck at the M logo(I can get to the stock recovery) and I want to know if there's a way to get to Clockworkmod.
I have Koush's bootstrap and Clockworkmod installed, so all I need is something that will trigger the bootstrap.
The backstory is that I was uninstalling Blur applications from ApeX and got a little overzealous, and now it won't boot(probably waiting for an application that's never going to start).

Ive heard that if you hold the down volume button when powering on, it will send you to bootstrap.
Sent from my DROIDX using XDA App

IWHBYD said:
I have a rooted X stuck at the M logo(I can get to the stock recovery) and I want to know if there's a way to get to Clockworkmod.
I have Koush's bootstrap and Clockworkmod installed, so all I need is something that will trigger the bootstrap.
The backstory is that I was uninstalling Blur applications from ApeX and got a little overzealous, and now it won't boot(probably waiting for an application that's never going to start).
Click to expand...
Click to collapse
Try plugging in a usb cable and pull the battery and put it back in, turn it on with the usb still in.
Sent from my DROIDX using XDA App

I think you're in for an SBF Flash. I had a similar problem the other day (tried to install a new rom...foolishly didn't make sure the battery was charged.) I tried all the above and then wound up doing a flash. Once I was back to stock the then gained root (another story) I quickly loaded Bootstrapper & restored my primary ROM (Darkslide 4.1) and am now a happy camper again.

I eventually gave up and SBF'd to stock, rooted, and then reinstalled ApeX. I was able to keep /data through the whole process, so I didn't lose too much. Is there any way to set up clockworkmod that it will always load in place of the default recovery system?

IWHBYD said:
I eventually gave up and SBF'd to stock, rooted, and then reinstalled ApeX. I was able to keep /data through the whole process, so I didn't lose too much. Is there any way to set up clockworkmod that it will always load in place of the default recovery system?
Click to expand...
Click to collapse
Install Koushs bootstrap recovery.
Sent from my DROIDX using XDA App

bigshotrob22 said:
Install Koushs bootstrap recovery.
Click to expand...
Click to collapse
I've had it installed the entire time. By default it only bootstraps/loads clockworkmod if you tell it to(specifically you need to be able to write to /data/.recovery_mode) so you can't just boot into it when your phone is off.
What I want is a way to essentially replace the stock recovery app.

IWHBYD said:
I've had it installed the entire time. By default it only bootstraps/loads clockworkmod if you tell it to(specifically you need to be able to write to /data/.recovery_mode) so you can't just boot into it when your phone is off.
What I want is a way to essentially replace the stock recovery app.
Click to expand...
Click to collapse
So does Koush and the rest of the Droid X owners...

Rubix has this feature sorta. If u install rubix drod implemented a beta fix that should boot into recovery if the battery is left out for x mins typically 3-5. From what I understand as long as the /system isn't formatted after installing rubix even if u use a different Ron this fix will still work. Might be worth installing rubix just to get this feature... and chances are if u haven't tried it before u might not want to leave rubix

Unless someone cracks the bootloader there is no easy to overwrite the stock recovery on droid x
Sent from my DROIDX using Tapatalk

Coming from an Unrevoked Forever Incredible, I've been searching for the same thing. Found this on another forum:
Getting Into Clockwork In a Pinch for Droid X
I saw a write up on this in another thread and I thought we needed it here too. I use this trick a lot and took it for granted that everyone knew it. Say you can't get into your phone to reboot into recovery through the Bootstrap App. Here are the Steps to get into Clockwork and Restore a Backup.
1) Make Sure your Phone is Plugged into the Charger.
2) Battery Pull.
3) With the Phone still Plugged into the Charger replace the Battery.
4) Wait until your Phone enters the Charging State. ( The Battery Icon Charging)
5) Hit your phone's power button, it should Boot into Clockwork Recovery. It works like a Charm for me everytime.

I figured that^ out on accident. If your stuck in the M you obviously have to battery pull but this will also work if you just reboot with a wall charger plugged in.

If you install the liberty rom, there is a feature that allows you to go into CWM every time you turn on the phone in the settings menu

Cyanogem Mod - stuck on boot screen

Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.

Do you have a custom recovery like Amon_RA or ClockWorkMod installed?

cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.

uansari1 said:
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
Click to expand...
Click to collapse
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do

That's what I had to do. Mine also got stuck.
Sent from my Nexus One using XDA App

Hollow.Droid said:
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
Click to expand...
Click to collapse
Agreed. I was just referring to what to do if you're stuck on the X or in a boot loop. ;-)
Sent from my Nexus One using Tapatalk

You're stuck with stock recovery. Reboot back to ROM, install recovery, only then reboot to install ROM.

Hey guys I'm having a similar problem, however my phone gets stuck on the initial nexus screen. I've been working on the phone problem for the better half of the day and this is what i've done, what works, and what doesn't.
WHAT I'VE DONE:
Full wipe, including Devik
Played around with installing different radios.
Download CM7-RC1 from CWM and the computer
WHAT WORKS:
MIUI Roms
Stock Gingerbread Rom
MY Back-up, which has CM7 Nightlie #45
WHAT DOESN'T:
All Cyanogen Mods
I even tried the CM6.0
So I'm a little stump on how to get my phone to run the latest Cyanogen or matter of fact, any CM Roms. Maybe my phone wants something different in her life
Any help will be great guys...thx

How much time did you wait?
Did you try erasing /system?

Well I just waited for 5 hours leaving it on the initial Nexus screen, in hopes it might do something, but it was to no success.
/system? not quite sure where that is... I am assuming it's in the roots... I can only do what I can from the recovery.

Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.

cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
Whenever you see "little green Android Logo and Exclamation", you can press volume up and power button together to get into the bootloader menu and reboot your N1. It seems like your custom recovery did not work. Try to flash Clockworkmod recovery 2.5.1.4 (not 3.0.0.5) or RA recovery again. It may help.

Jack_R1 said:
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
Click to expand...
Click to collapse
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?

LeoGingerbread executes "format /system", that actually works and cleans the remains of the old OSes. Some other ROMs do, too.

armyshawkeye said:
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
Click to expand...
Click to collapse
Because you still have the stock recovery installed, that is how you access the menu for it.

Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
http://db.tt/wdeoIMI
Sent from my Nexus One using XDA App

danger-rat said:
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How I flash this? As a update.zip?

Yes. I believe it executes "FORMAT SYSTEM:" command, maybe more than once.

Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App

danger-rat said:
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
CW Recovery has options to format system, and other partitions, under Mounts and Storage.
Sent from my Nexus One using Tapatalk

[Q] Can't get into hboot or clockwork?

Search function is down but I did go through a few pages of threads looking for what was going on and no luck but I apologize if this has been solved somewhere else.
First off I would rate my rooting know-how as beginner to intermediate. I've jailbroken/unlocked multiple iPhones awhile back and have rooted/flashed roms on a cliq, mts, my3g, and this mt4g before.
I recently returned my current mt4g back to stock rom and unrooted. I do not think I turned s back on but I should have double checked before.
I currently have root and flashed clockwork and am trying to flash CM7 (I had ran it before on this phone as well). I have an issue right now where I cannot get into clockwork recovery as it will just sit at the mytouch logo forever and if I try and volume up and power into recovery all I get is 3 vibrations and a flashing amber light.
I can boot into the stock (but rooted) rom.
Any ideas? I feel like my recovery is broken or something but this goes beyond what I know. Any help would be great and any information you need I'll be happy to provide.
myTouch 4G, rooted, s (probably) off, stock rom, clockwork says i'm on 3.0.2.4

After reading that, I'm not fully convinced you actually have root and S-OFF. If you're sure you do, download ROM Manager from the Market and use that to install a fresh copy of CWM recovery. Also make sure the "fast boot" option is turned off somewhere under Settings. At that point, there should be nothing preventing you from getting into recovery if you have perm root.

I've got ROM Manager and it has SU permissions and I have the latest recovery flashed but I am still stuck on mytouch logo or the 3 vibrations/amber light when I try to get to recovery. If I reboot there is still no problem getting SU in terminal emulator or ROM manager or anything.
Fast boot is off as well. Thanks for the help so far.
Any ideas?

I don't often boot into recovery manually since most custom ROMs have an enhanced reboot menu with a recovery option, but if memory serves, I believe the key press combination is actually Power + Volume Down, not up like you mentioned in your OP. Give that a try.

Man I am really crazy. Here I am a tmo rep and also a novice modder and I'm hitting power + volume up.
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Thanks for the fresh set of eyes!

breakaway87 said:
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Click to expand...
Click to collapse
After flashing CM7, the phone hangs at the myTouch screen when attempting the first boot?

From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.

breakaway87 said:
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
Click to expand...
Click to collapse
What if you select the "boot into recovery" option in ROM Manager? Does the phone reboot into CWM recovery? (you should see the main CWM menu in orange text)

Boot into recovery takes me to MT4G logo and hangs.

breakaway87 said:
Boot into recovery takes me to MT4G logo and hangs.
Click to expand...
Click to collapse
So you don't have a good installation of CWM. Open ROM Manager again and re-flash a fresh recovery. I think there's an option to wipe your existing recovery beforehand, so if you see that, select it. You need to get a working recovery image before you can do much else.

Deleted current recovery and I confirm my model again and it takes a total of 5 seconds. Trying to reboot into recovery again after and I still hang at MT4G.
I hate it when you know something you need to do but you've been working on it so long you can't come up with new ideas.
Thanks again for the help.

Sorry multipost since it didn't register on my computer the first time for some reason

Yeah sorry man, I've never heard of a situation where CWM stubbornly refuses to install. If you have the engineering bootloader, you could manually flash it that way, but that's my only other idea.

Alright well thanks for all the help man, I'll dig around and pick up tomorrow.

I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help

breakaway87 said:
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
Click to expand...
Click to collapse
Sure, glad you figured it out.

Phone boots into recovery from power off state

Hi,
my friend's Droid X has Gingerale 3.0 rom on it, and the latest clockwork recovery from rom manager. Weird thing is his phone reboots into recovery whenever he turns it off/reboots it. He can get it to boot normal after selecting reboot from the recovery menu. It's just weird and I'm wondering if anyone knows how to fix it.

I need an answer to this also!
*DroidX Running Liberty 3 v2.0 @1.2ghz*

.ili.music.ili. said:
Hi,
my friend's Droid X has Gingerale 3.0 rom on it, and the latest clockwork recovery from rom manager. Weird thing is his phone reboots into recovery whenever he turns it off/reboots it. He can get it to boot normal after selecting reboot from the recovery menu. It's just weird and I'm wondering if anyone knows how to fix it.
Click to expand...
Click to collapse
do you have droid 2 bootstraper installed

Mine does this too, but it ain't no thing. I just reboot it thru the recovery menu and it reboots normally.
No big deal.
I actually think it's a good thing.

Agreed out had saved my ass a few times I think it Droid2 bootstrapper
Sent from my DROIDX using XDA App

This is probably a result of having Jakebites mod on the phone.
There's an toggle in the modcentral script to ALWAYS boot to CWR on reboot, at which point you select "reboot" from the recovery menu and it loads as normal. It's intentional, in case you end up flashing something that screws up your boot process and need to restore a nandroid

The best way to get rid of it is to SBF your phone
Sent from my DROIDX using XDA App