My Motorola Droid X just will not boot up, my bootloader is 30.04 and i SBF'd the .621 Update.
The phone wont enter the "charge mode" (Need to Charge!!!) or recovery (Stock) and is Stuck on the Red Motorola "M"
Any Thoughts?
EDIT: Nevermind, got to recovery and it all started working after a reset!
Always perform a reset after running an SBF.
Sent from my Liquid X
Related
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Hey there,
I had something similar back when I tried to root my evo 4g the first time, what I did was go to the carrier store (in my case Sprint) and acted like one day just started to act weird and they replaced it for its "factory defects"
P.S. Some stuff I learned was that I damaged the usb port.
GOOD LUCK
Sent from my beloved EVO 4G
rpierce said:
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Click to expand...
Click to collapse
a trick to get into clockworkmod recovery, turn the phone off and plug into the wall, try to turn on....well not really try, turning on the power button should boot to cwm
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Bricked in need of help
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Macificient said:
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Click to expand...
Click to collapse
U might try pushing the power button instead of the search button when the droid and exclamation mark are on screen. Hope that helps
TappaTappaTappa
sanjeeva7 said:
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Click to expand...
Click to collapse
U might have a corrupt file missing something... try downloading the sbf file from droidmodderx's website he's got sbf for froyo and gb
TappaTappaTappa
Did you upgrade through SBF, or OTA?
What is your bootloader version?
Sent from my DROIDX using XDA App
You can try the .602 sbf linux boot disk found HERE
It works every time for me and on any computer (that can boot from a cd)
D.
sounds like, judging by your bootloader version...you may be needing to find the 2.1 sbf, flash to that, take the OTA to gingerbread.... and you may have a little more luck with current roms once your bootloader is 30.0#
Just SBF. That will fix your trouble. Almost Impossible to "Brick" the DX.
Phone was rooted with .596 (2.3) and working perfectly for weeks. Gave to my daughter who lets the battery run out completely yesterday.
Now:
Trying to go into recovery = android dude with triangle exclamation point
Trying to boot normally = motorola sign, droid sign, animation starts, phone vibrates once like normal, notification lights once like normal, animation slows down, screen goes black, phone completely unresponsive, have to pull battery to retry
Trying to plug it into computer = screen turns on showing "no service", is in airplane mode, can't use touchscreen to unlock, screen goes black, can't get it to come back on....Can access the SD card
Any ideas how to fix this?
Looks like you need to sbf
DROID X running liberty GB V.8
yup sbf...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
got into bootloader was 30.04 so I used the 2.3.34 system only .sbf file. everything said it worked ok, got to where RSDlite said to manually power up phone. Stuck at Red motorola Circle. Tried to go into recovery, get to the android and ! again. Try to hit search key so I can do a wipe as is suggested in these circumstances and nothing happens...just sits there...Multiple attempts at both still stock on Motorola or android/!
ideas now?? thanks for the help btw
EDIT: Got it, Did SBF with full version instead of the system only and that made recovery work, did the wipe/reset and all is working again
thanks all
Nice, was about to say a full sbf is what you need
DROID X running liberty GB V.8
tried to install cm9 on my atrix with cwm. wiped cache, dalvik cache, everything. idk how i could have gotten it wrong. then i tried to boot and it has the moto logo with "failed to boot starting rsd mode". but it never actually starts rsd. fastboot won't work either. tried pushing volume down+power and it shows moto logo, then flashes some white words on the screen. too fast to actually read them. then complete power off and won't power back on unless i do a battery pull. any help?
try to flash with service or full stock rom 2.3.4
When you get the RSD message did you try a Vol up to start RSD mode?
Also try flashing as it stands. I had a similar issue and was able to still flash with RSD Lite even though it did not indicate RSD was started. (Just hung at the screen)
I got this when I tried the ota update while being rooted and a locked bootloader. I reflashed with rsd lite to the original software release and it automatically did the ota.. Now working..you can pull the battery and hold volume up and power till you see fastboot and use volume down till you see android recovery and try that.. I'm coming from Samsung so I haven't really worked with moto yet..
Sent from my MB860 using XDA App
is your battery charged?
try to reunlock your bootloader with pudding, then flash CWM and try to reflash ICS
??
So. I have NO idea how this worked but my phone is fixed. I got into RSD and tried a stock SBF file. it failed. phone wouldn't boot but wasn't hard bricked. but it DID let me into recovery. tried reflashing the CM9 rom that i was ORIGINALLY trying to put on there. didn't work. battery pull. and it booted up to a working 2.3.4. I'm confused out of my mind. but it works now. now to attempt CM9 again
So as my wife tells it she received a text message then the phone shutdown and went to the bootloader screen. She was running Liberty2 v3? up until now.
The phone boots to the bootloader showing:
Boot Loader
D2.37
err:A5,69,55,00,27
Ready to program
USB
The standard bootloader schpeal.
Unfortunately I can't do anything to get beyond this. I have tried SBF to 2.3.20 and 2.3.4 both come back to the same screen. Cannot access recovery by holding X or the down volume button.
On boot the phone shows the Red Moto "M" logo then fails to the boot loader.
HALP!
You don't see the M logo when you go into boot loader. Hold the up arrow on the keyboard as you power on. Boot loader will be the first screen that you come to.
Don't know what to tell ya. I can't get into recovery no matter what keys I press. I get the "M" logo then it fails into the boot loader with the above error.
I can ONLY get to the bootloader no matter what I do. No SBF files seem to work and I cannot get to recovery to try and wipe data/cache to fix the bootloop. Basically I'm stuck at the bootloader and can't do anything to get past it.
twiceover said:
I can ONLY get to the bootloader no matter what I do. No SBF files seem to work and I cannot get to recovery to try and wipe data/cache to fix the bootloop. Basically I'm stuck at the bootloader and can't do anything to get past it.
Click to expand...
Click to collapse
I'm pretty much in the same situation.
Wish someone with better knowledge than I can pipe in.
Been stuck like this going on 2 weeks now.
There has to be an .sbf to flash that'll work.
phirewire110 said:
I'm pretty much in the same situation.
Wish someone with better knowledge than I can pipe in.
Been stuck like this going on 2 weeks now.
There has to be an .sbf to flash that'll work.
Click to expand...
Click to collapse
Yeah, today I'm in search of a DInc2 to replace it. Luckily I do have a Droid1 that uses the same battery so I can charge it and keep trying various things to get it working. Just sad that a phone that was perfectly good one second is toast in minutes. She could have at least dropped it and had it die that way...
Bricked D2
bump. D2 Bricked. Saw there was a sbf for D2 global, but those of us with bricked D2 seem to be out of luck for now. Oh well, I guess i don't need a phone for a while. . .
Did you guys take the newest Verizon Over the Air updates?
OK so my droid x has only booted into recovery mode for a while and I just left it that way after taking the battery out... I decided to try and fix it yesterday. I was fallowing this guide (droidxforums(DOT)com/forum/droid-x-sbf/12015-complete-droid-x-sbf-flashing-guide.html#post106311) and my bootloader is at 30.04. I was doing it on windows and used the latest RSD Lite. I think I need a full SBF so I tried the 5th one down (VRZ_MB810_2.3.34_1FF_01.zip) on this site sites(DOT)google.com/site/motosbf/droid-x-sbf-files
I SBFed it and every thing went fine... it said PASS and I thought I was done... correct? but when I rebooted it just booted right back to the bootloader. Plz Help
Does the bootloader screen happen to say MEM_MAP BLANK?
Sent from my Black Iced X
newmanx4 said:
Does the bootloader screen happen to say MEM_MAP BLANK?
Sent from my Black Iced X
Click to expand...
Click to collapse
Yes It does here is all it says:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
EDIT: Solved just SBF'ed .621 and worked perfectly! Thnx
Glad you worked it out. That's what happens when you try to install a previous system version over .621.
Sent from my Black Iced X