Database Users

[Q] Help!! I bricked it

Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help

Bigstew33 said:
Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help
Click to expand...
Click to collapse
Looks like you'll want to SBF the device. Google search on how to SBF the Droid X and you should come up with some really good guides. Make sure you flash to 2.3.320 if you want to use the latest and greatest that Team Defuse has to offer. I would post a link to one of the guides, but I'm away from my computer today.
Sent from my DROIDX using XDA App

The only way. Into clockwork is pull battery so he says.if not send me your email to [email protected] I have the links.or download
http: market_android_com search?q=pnamerg. teamblackhat.leakloader
Its an app on marketplace call teamblackhat downloader
Sent from my DROIDX using XDA App

I have rsd lite and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf I open the RSD and choose the sbf file but RSD doesn't find the phone. there are drivers loaded says Motorola Flash Interface v. 3.2.5.0. I have it in the bootloader says ok to program transfer mode usb. Thoughts
Thanks

Windows 7 64bit pro gives some difficulty with recognizing the phone. I suggest removing the motorola drivers and downloading them again.
I got it to work by plugging my phone in, then installing the drivers immediately after. It is screwy sometimes though.
Also RSD has device ID options. change that and see if it recognizes it. I also find that sometimes if I plug in my phone after RSD is open it finds it.

wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later

Bigstew33 said:
wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later
Click to expand...
Click to collapse
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.

http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html
See code corrupt error section.
The easiest option is to charge your battery in another X.

amasse said:
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.
Click to expand...
Click to collapse
yes I charged the phone to 100% and tried again and again the battery died before it finished. the sbf file I have is 280 Mb. If there is a smaller one then maybe it will work

It's more likely that the SBF file you have is bad or there is still some sort of USB driver issue going on. Try downloading it again from wherever you got it.
The phone should not go from 100% to dead in an hour. Also the SBF flash shouldn't take nearly that long.

for now I am stuck. I can't get the phone to charge the battery any more. When I plug the phone into the wall it just goes to the bootloader screen by its self and has an error number and a message that the battery is low. So I ordered some batteries with a wall charger. Once those arrive I will try again. thanks for all the help you guys are giving me. update later date

Can't access recovery!

OK, so I have a D2 that someone gave me. It was completely stock (not rooted), but had all of their stuff on it still so I decided to do a factory restore through the android menus. The process started and the phone got stuck at the "M" logo, I left it for a few hours, and never budged.
I can NOT get into recovery, holding "X" and power on battery or connected to USB does nothing, have tried about 50 or 60 times now.
I can get to the bootloader and flash a new sbf (tried 2.3.20, 2.2.20, and downgrading the bootloader to d2.35) aside from the d2.37 bootloader I don't know of any other sbf's to try untill the GB one leaks, and who knows when that will be. I am using RSD lite 4.9 on win 7 x64, and 2.3.20 does not error out, also it identifies the phone as "s flash omap..." something instead of A955 or droid.
Sorry for the lengthy post, any help would be appreciated.
Edit: I tried flashing the 2.3.20 sbf from an ubuntu live CD with no joy. I just don't understand, i'm not getting any errors with ADB, it completes just fine, so recovery should be there for me to go into. The better part of 2 days trying to figure this out now.

Just a quick question, is recovery included in 2.3.20 full sbf?

Try it on a different computer. That worked for me. S flash is OK. As long as it says connected, you're good. You need to sbf. As long as you can get into Bootloader (2. 37)you can sbf.
Sent from my DROID2 using XDA App

That was the next thing I was going to try, need to get an OS on my old laptop to try, I have been busy so I should get to that sometime before the weekend. Dug out an old OG Droid that had the same issue that I could never figure out too, and got a custom recovery flashed, but no success on the full SBF or restoring a backup. Hopefully it is just this PC that is not playing nicely.
Thanks for the suggestion.

You can't get into recovery after you SBF? Is that what you mean?

wrichards2009 said:
You can't get into recovery after you SBF? Is that what you mean?
Click to expand...
Click to collapse
Exactly, it's like recovery is not there. Powering up while holding X does nothing, all I get is the "M" logo. I've let it sit and eat a whole battery just sitting on the "M". I will try to flash on another computer or two tonight and post my results.

Well I finally had time to try on another computer, and no luck. Used a freshly downloaded SBF, moto drivers and RSD Lite 4.8. Also I hadn't thought to check the logs before, and the FlashErrorLog has 4 errors, ERROR: AP Die ID, BP Die ID, AP Public ID and BP Public ID.
Everything went same as before, RSD completes with no errors. (well almost completes when I use my Motorola branded cord, stops at rebooting phone, and with my wifes LG branded cord, it reboots into the bootloader automatically, strange)
If anyone else has any ideas, I'm just at a complete loss here, willing to try something drastic at this point.

Having a similar problem, so hope you don't mind me piggybacking on your thread. I'm running 2.3.3 rooted on my D2, and I cannot boot into recovery either, but also can't get SBF to recognize my device on any computer. Any ideas?

How to get into Clockwork Mod
Is there a way to enter Clockwork MOD recovery on a rooted phone Manually? I am away from a computer, phone seems to be bricked need to get into recovery MANUALLY ...................

[Q]can't install roms, failed SBF, now what

Tried to install several roms but every time it says it can't verify the info so I decided to do SBF.
Plugged in phone PC downloaded motoflash driver even though I have latest moto usb driver and shows up as this in RDS lite
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00C106
DRM Version: N / A
Phone Type: Engineering (1D1D3410D773020000003C060000)
It goes through a few things and then gets to flashing but says FAILED phone is not compatible with multi-interface super-file. (0x703B)
I verified the SBF was the correct one, wasn't corrupt and was the correct md5 and tried a couple times with the same result.
What do?

I have this same issue. Can anyone tell us what that error means?

Depending on whether your sbfing froyo or gingerbread you need the most recent sbf of the two
Sent from my MB860 using XDA Premium App

Same problem.
I am having the same issue. I think I may have actually completely bricked my phone. I didn't think it was possible.
I was attempting to use ROM Manager to flash to MIUI. It then went into a boot loop. However, it does not even hit the eye. Just the 'M' screen.
When I try to boot into recovery, I get Andy with the triangle exclamation point, but the search button does not bring up recovery.
Most of the time my XP PC tells me that it does not recognize the hardware. When it does and I try SBF using RSDLite (4.8 and 4.9), I get the same as above and the log have hundreds of these entries:
[0x0000137c] E(08) [1000] CPSTSerialTIHelper:rocessPingCommand - Failed to get DIEID ACK
I have Moto Driver updater 5.2 with the latest droid drivers.
I tried using SBF_Flash for the MAC, and It gets stuck on "Waiting for phone..."
My guess is that the component that communicates from the phone is corrupted. Any thoughts or suggestions?
Thanks

First, to get into stock recovery you have to use the volume rocker once you get to andy, not the search ket (atleast seach hasn't worked for me, and you need to press both at once)
Second, you need to go into bootloader (idk if you have, but I didn't see it mentioned)
Third, make sure you have the correct SBF file (I use the triplethreat full sbf, which redoes kernel and system)
Fourth, I haven't seen a phone bricked yet, and I've been doin this for a bit of time, that was more in the early days of android.
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.

I fixed my issues. It turns out that both my PC and My cables were having issues. I used a new machine with a fresh Moto cable, and was able to flash. Took 2 attempts, though.
Good luck

Great!! Glad it worked!
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.

[Q] reboot loop, can't get Windows to see phone to SBF, etc

Okay - I can't seem to find a single thread that has a working solution to this.
Had Gingerale 2.0 on the Droid X. Was acting funny so decided to go up to CM7.1 now that it's supported. Had trouble getting into Clockwork via ROM Manager then via Bootstrap. Was about to try re-rooting (even though it is definitely rooted) but then ran into this problem..
First, when in standard recovery, I could not install the CM ROM because it failed to match the md5 sum (I'm presuming it's an md5). Not sure if that's normal, though, since it's the standard recovery and not clockwork.
After a system reset, which I did read somewhere, now the phone is stuck in a loop. Gets to the "DROID" noise, then the red-eye circle thing, then back to "DROID."
I cannot get the phone to show up on a computer - Win 7 in VM, Win 7 on laptop, Win 7 on desktop - so that I can try doing an SBF on it (which I have never done, but I think I have all the parts).
Thoughts on how I can get it to show up? Or other options?
thanks.

You may need to install drivers if you haven't already.
Try the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App

Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.

kaiyen said:
Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.
Click to expand...
Click to collapse
Try setting the connection type to either 'charge only' or 'PC mode'. Also try cycling through the different options.
I also would definitely recommend going the Linux route via 1kds's bootable SBF distribution.
Sent from my DROIDX using XDA App

The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.

kaiyen said:
The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.
Click to expand...
Click to collapse
Sorry for bad information lol.
The phone will enter bootloader mode successfully though?
Sent from my DROIDX using XDA App

No problem - the hardest thing is that I can't quite find the exact problems I'm having when doing searches. So the "usual" answers dont' seem to apply.
Bootloader mode - not 100% sure what that is. It starts up, I get the "M" and then the "DROID" sound. Then I get the spinning robotic eye thing, then it goes back to DROID. Over and over.
I can go into the standard recovery but not bootstrap nor clockwork (both of which I have installed in the past) and I know it's been rooted successfully.
I have wiped the entire phone while in the standard recovery several times but no luck.
thanks for any help. Worst case, I'm going to Verizon tomorrow and just going to show them it not working over and over, and try to get all my data off of it. Get a new phone. But I'd like to figure out what's up and/or get CM on here eventually.
allan

There's your issue.
Your phone must be in bootloader mode to SBF.
Hold both volume buttons and press the power button (press, NOT hold) and your phone will boot into bootloader mode.
The bootloader screen should show your bootloader version and say 'OK to program'.
From there, simply use RSD Lite or the Linux method to SBF.
After you SBF your device you must boot into stock recovery and format data and cache.
Sent from my DROIDX using XDA App

I haven't tried doing the SBF yet but THANK YOU. Ever reference I got to getting the phone into any kind of mode was just recovery. I had not found this bootloader mode option until now. Just missed it or whatever in other posts!

[HELP] Stucked in bootloader mode, code corrupt, enable to flash [HELP]

Hello everyone!
I wanted to flash my milestone 2 with the 2.3.4 sbf file but during the process, an error occured and now, my phone is booting by himself in bootloader mode. I've got this message telling me that the code is corrupted and when i try to flash it using RSD lite, the phone is detected but the process fails every time.
I've looked a bit around on google and the only solution that i found is to boot in OpenRecovery but i can't boot with anything else than Bootloader...
If you have any ideas, i'll be happy to read them. =)

You should probably flash/reflash a Milestone 2 specific SBF file.
Sent from my Transformer TF101 using XDA App

I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...

goeland64 said:
I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...
Click to expand...
Click to collapse
It sounds like the battery got too low. Try using a different battery.
Sent from my DROIDX using XDA App

or by a $5 battery charger from amazon

The battery won't charge but the thing is that just before flashing with the 2.3.4, i had about 50% battery so technicaly, i should have some. I'll try with another battery, i hope it will work. =)