Just flashed to Blur 3.0, bricked my phone.

Discussion in 'Droid 2 Roms' started by ElShotte, Dec 23, 2010.

  1. ElShotte

    ElShotte New Member

    Joined:
    Dec 9, 2010
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Okay, so I need help. I just flashed to Blur 3.0 and now my phone just sits with the "M" logo displayed. After I flashed, the phone actually booted into Android, but my colors were all inverted, so I tried to Power Off and Boot it again, nothing.

    Here's what I did:

    From Squidly 2.3.20 Installed

    • Recovered Backed up Stock ROM
    • Wiped Data
    • Wiped Cache Partition
    • Installed Blur 3.0

    And now, I have no phone :icon_eek:

    Okay. One thing that raises a flag is it updated the kernel. Will that be a problem? I know that if I hold the Up Arrow I can boot into USB Recovery, I'm at my parents for the holidays and don't have access to RSD Lite. I also held the X key at Boot, and it gave me the Blue recovery menu, but there's no option to restore backed up ROM. Is there a Key to boot into Bootstrap Recovery? And then, even if I install the stock 2.3.20 SBF, will the updated kernel be a problem?
     
  2. ElShotte

    ElShotte New Member

    Joined:
    Dec 9, 2010
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Wait, I think Im getting something. Booted into the ROM Manager Menu (Blue Menu, Holding X) did another User Data and Cache Wipe, now Im on the Red Android Logo... update, I got the Welcome to DROID2 screen with normal colors. Do I stay with Blur 3? I guess Im gonna have to restart the phone see if it boots back up... if it does, I guess Im good for now (atleast it works).
     
  3. hookbill

    hookbill Premium Member Premium Member

    Joined:
    Nov 30, 2009
    Messages:
    19,502
    Likes Received:
    7
    Trophy Points:
    168
    Location:
    N.E. Ohio
    Ratings:
    +7
    Sounds similar to something that happened to me when I installed 3.0.0. and went back to 2.3.20. The kernel was indeed an issue and when I booted I got the M Logo only. I pulled the battery and got past the logo but I could tell my D2 wasn't acting right.

    Now here comes the bad news. I had to SBF 2.3.20 to fix it. I don't believe there is any other way.
     
  4. ElShotte

    ElShotte New Member

    Joined:
    Dec 9, 2010
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Hey hook, if I flashed with a 2.2.15 SBF would that bring me down to 2.2.15 and I could install 2.2.15 themes and ROMS?
     
  5. Jboxen

    Jboxen Premium Member Premium Member Developer

    Joined:
    Jun 15, 2010
    Messages:
    902
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Rochester, NY
    Ratings:
    +0
    Sounds like you didnt mount system. Thats a big no no.
     
  6. ElShotte

    ElShotte New Member

    Joined:
    Dec 9, 2010
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    You're right, I didn't. What do I do? I still haven't rebooted my phone because I am afraid it won't boot back. I'm assuming install 2.3.20 SBF then go back to custom ROM? Or should I just try to boot into recovery from the phone while I still can, mount the system, then install the Blur 3.0 ROM again?
     
  7. captainoftheworld

    captainoftheworld Member

    Joined:
    Dec 16, 2010
    Messages:
    318
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Bootstrap and then reboot recovery from the app, you'll be fine.
     
Search tags for this page
can i use my motorola blure with cricket
,
how do i flash a moto blur
,
how do you put battery in a motorlablur
,
how to flash an at&t motorola blur to cricket
,
how to flash motorola blur
,
motorala blur on cricket
,

motorola blur bricked