Stuck in boot loop (tried flashing new spf)

[1KDS]

yeah, that's the 2.2.1, 2.3.15 was the_gift2

[Ads]

[Stereosound]

Interesting! I'm grabbing it now. About 45 minutes before I leave so if this works it'll be great! Went and activated a super old generic VZW phone and I'm already dying to get

[1KDS]

good luck, hopefully it works, I'm afraid it's done for

[Stereosound]

Okay, flashed the new sbf, it came up with this screen:

Bootloader
30.03
Err: A5,70,70,00,1F


MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connet USb
Data Cable



Can't get hte phone to book into recovery now, suggestions? (;
-- Edit: Just read up a bit, possible I flashed an older file? It was the_gift2, dunno if I'll have much time to look into it before I leave though I'm afraid!

[1KDS]

I think it's bricked. You flashed the wrong sbf first (the happy holidays one). Are they sending you a replacement because of this or another reason? You may have trouble getting warranty credit for a phone that reads these codes. May have to use insurance (if you have it)

[Stereosound]

They're sending me a replacement because the phone wouldn't boot, it'll be at my door in two days (when I'm not here). I should have left it, heh. No way to unbrick? That's what I get for rushing into things frantically, hah. I don't know when it's investigated, hopefully the "trial" is over.

[1KDS]

I'm not sure there is any way to get it back but someone else may have an idea.

[Stereosound]

I thought the 2.2 sbf was needed to actually unbrick it -- it was when you installed the 2.2 OTA and went back to 2.1 SBF because the bootloader changed? I'm gonna look into it a bit more.

[1KDS]

Asked a couple people and they agree, your phone is unfortunately bricked. You'll have to deal with the clunker phone till you get your hands on the new DX.

[psychotic_penguin]

If you tried to use an SBF file lower than the current OS you were on, then it will semi-brick like that.

If you were on 2.2+ and tried to SBF to a lower one like 2.1, then it will probably brick like this. In that case, you can try to SBF to 2.3.320 like some have done and that may work then flash System SBF for 2.3.340 after that.

Here's .320 DROID X 2.2.1 Leaks, Updates System to 2.3.20 - Droid Life: A Droid Community Blog
and Here's .340 for after that: DROID X 2.3.340 System SBF Released for 2.3.320 Leak Users - Droid Life: A Droid Community Blog

Granted this is a stretch but it may just work.