I am trying to help a friend recover his DroidX and have an issue that I've never seen before.
This is on stock non-rooted DroidX. (Will be rooted soon I hope...)
His wife was using the phone when the it froze and rebooted itself.
When it did, it went directly into bootloader mode.
A couple of battery pulls etc. and finally got the phone to boot but now it will not connect at all. The signal bar show the red circle/slash across it.
In about this phone the Baseband says Unknown as does the ERI and PRL.
He tried *228 and doing a factory reset and even did a hard reset from the recovery screen.
It's out of warranty and V says they cannot help him so now he is going to bring it to me. I have lots of experience with the OG Droid and some with my new Bionic but I have never heard of this issue.
If/when I get it going again, it will be rooted and possibly ROM'd, depending on what he wants.
Searching the forums, I found a few posts but none seemed to have any solutions.
My first attempt is going to be the .sbf recovery from the All Things Root section.
I am wondering if anyone has come across this type of error before?
It seems to me this could be an actual hardware issue.
Thanks.
This is on stock non-rooted DroidX. (Will be rooted soon I hope...)
His wife was using the phone when the it froze and rebooted itself.
When it did, it went directly into bootloader mode.
A couple of battery pulls etc. and finally got the phone to boot but now it will not connect at all. The signal bar show the red circle/slash across it.
In about this phone the Baseband says Unknown as does the ERI and PRL.
He tried *228 and doing a factory reset and even did a hard reset from the recovery screen.
It's out of warranty and V says they cannot help him so now he is going to bring it to me. I have lots of experience with the OG Droid and some with my new Bionic but I have never heard of this issue.
If/when I get it going again, it will be rooted and possibly ROM'd, depending on what he wants.
Searching the forums, I found a few posts but none seemed to have any solutions.
My first attempt is going to be the .sbf recovery from the All Things Root section.
I am wondering if anyone has come across this type of error before?
It seems to me this could be an actual hardware issue.
Thanks.