Root Stuck at Motorola logo

[Sprocket]

I've been running on Apex 2.0 for about a month without issue. Last night the phone locked up and would not respond to any key press so I pulled the battery. Since then, powering on the phone stalls at the white motorola logo endlessly. I've tried SBF by way of RSDlite and the linux cd method, note that I've SBF'd many times before and have never run into an issue. Holding Home and powering on does not bring up recovery. Swapped with a fully charged battery with no additional luck. Any more ideas?

 

[emaN resU]

I've been running on Apex 2.0 for about a month without issue. Last night the phone locked up and would not respond to any key press so I pulled the battery. Since then, powering on the phone stalls at the white motorola logo endlessly. I've tried SBF by way of RSDlite and the linux cd method, note that I've SBF'd many times before and have never run into an issue. Holding Home and powering on does not bring up recovery. Swapped with a fully charged battery with no additional luck. Any more ideas?

Have you tried pulling the sdcard and try booting without it?
Just a suggestion.

Edit: When holding down home while booting, what does the phone do? If it looks like it is still on try the volume up/down button press. Another suggestion.

 

[Sprocket]

Booting without the sdcard does the same thing, white motorola logo.

Holding home, same, never gets past the logo to the exclamation point. Volume button didn't affect this.

 

[VoidedSaint]

wow that does seem like an issue you are having, have you tried booting without the battery? but the phone plugged into a powersource?

 

[Sprocket]

When the battery is out, the phone boots up right away without any buttons being pressed. Still stuck at the Motorola logo however.

Just my luck too, it's been a couple weeks over a year since I got the phone. Don't think I can exchange it now.

 

[z0mb13m4n]

Only suggestion I have, is to try a different SBF file. I'm imagining you were using the .340 SBF, try the .596 file.

 

[Sprocket]

I've used both 340 and 596. The 340 I've been using for months to try out different roms without issue.

 

[Aggie12]

Try using a different computer or a different usb port just to rule those out.

 

[Sprocket]

3 different computers and two different USB cables and still stuck. Folks and the Verizon store were less than helpful as well.

 

[Aggie12]

well damn... I ran out of options. I didn't know this could happen.

 

[z0mb13m4n]

yeah, this is a first. I'm really at a loss as to what to do now.

 

[VoidedSaint]

sounds like you completely bricked your dx.... i dont see how apex could have done it, you probably had an app that had malware and someone possibly got into your system files and corrupted it, not so sure, but im hoping that isnt the case