What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Big Problem

Factory reset should go back to stock....no mods. Sometimes helps if an install wasn't 100% error proof...

Sent from my DROID2 using DroidForums App
 
Ok, I got it re-rooted. I was able to get the Clockwork Recovery installed thanks to iwearhats' PM. Thank you again. I reinstalled Rom Manager, and it appears that my phone is updating to the new ROM as I type this.

It looks like it's done, and it appears to be booting correctly.

EDIT: It looks as though all it did was factory reset it again. None of the bloatware was back on it, and it wasn't updated to the new os. I tried the OTA update again, but it failed.
 
I just read this thread and it is a complete mess. First off the D2 is not the same as a D1 so you can't get advice from someone with a D1. Rom Manager is of no use for a D2. To do anything you need to have Bootstrap installed.

If you still need help drop me a private message and I'll help you.
 
I got Bootstrap now, and have it working in conjunction with Rom Manager. When I load new roms, it still wants me to do an OTA update, but the update always fails. It still says I'm on System Version 2.2.19.A55.Verizon.en.US. I want to update it to a later version.
 
I tried reinstalling all the bloatware, and it bricked my phone. It won't boot at all. It's caught in a boot loop. It starts at the Motorola M screen. It goes to the Droid logo, starts the red eye boot animation, then goes back to the Droid logo, and keeps repeating.

The boot recovery somehow got flashed back to stock, so I can't recover any rom backups I had with Clockwork Recovery. I can't get the SBF to work either. The factory reset didn't work either.

EDIT: Now it's just staying at the Motorola M logo.
 
Whenever I boot into recovery I get the stock recovery but if I do a battery pull and then immediately boot back into recovery it brings up cmr. Sometimes it takes three attempts but I can usually get in there. You might try that to see if you can get back in to cmr and flash a nandroid of a safe build.

Sent from my DROID2 using DroidForums App
 
Ok, I tried that, but I'm getting this error message:

ERROR: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE003003F Command: RQHW

Any ideas on how to get around this?
 
Be calm, many have been in your position ... it will get worked out.

I will help you flash the new sbf and that will get you updated. I also had issues the first time I tried to sbf. It is a learning experience that will help you in the future.

Flashing the sbf is a finicky process. Little things like where you have the file placed on the computer matters. I actually couldn't get it to work on one of my computers but it worked fine on a newer one.

I know you are in a frustrating situation but if we can link up I will help you get past this. A real good place to start on your own is the link posted early in this thread... "flashing a rom class" http://www.droidforums.net/forum/droid-2-hacks/91760-droid-2-hacking-rom-install-class.html

I will keep an eye out for a response. This is easily resolved :)
 
Ok, I made a breakthrough.

I followed the tutorial provided by your link MrKleen.

I changed computers, and tried a few times, but to no avail. I kept retrying getting into the bootloader, which usually comes up as the M, and is detected by RSDLite. This time it went to a DOS-like bootloader that said Battery OK. I connected it to the computer, but it didn't recognize it. I searched for drivers, and finally found one. RSDLite recognized it, and was able to flash it. The phone looks as though it is back to stock with all the bloatware.

How do you differentiate the phone from being in the M bootloader and the Battery OK bootloader? I don't do anything differently, it seems like the Battery OK bootloader comes up by chance.

Thank you all for all of your help.

Anyway, I'm glad I didn't have to go back to using my BlackBerry Storm.

dancedroid

dancedroid:byestorm:dancedroid
dancedroid
 
Back
Top