Official 2.2 brick...my fix

Discussion in 'Android Hacks and Help' started by neo4uo, Aug 22, 2010.

  1. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    My wife did the 2.2 update the other day and it got hung at the "m" screen. I have been using UD roms for awhile now and have never bricked a phone. I usually use Chevy's rom to overclock and top it off with cuttalot's themes. I love the whole custom rom option versus the official 2.2. After the official 2.2 bricked my wifes phonethe I tried several things to get it unbricked. The fix was going to an unofficial version of 2.2 lol. I ended up flashing with the clockwork or the other recovery program I can't remember the name. You can do some research on doing a install on custom Rom. The only thing is after the first install of the custom rom it hung on the m screen again. The difference is that this time I could boot back into recovery after a battery pull. I had to do a cache data reset in recovery and install 3 times to get past the m screen. The difference again is with the official 2.2 you couldn't go back into the recovery once I got locked on the m screen. All I have to say is this forced my wife to go to a custom rom. I think she is glad she didn't have to wait on a new phone and she likes the features of UD 7.0 ;). Any? Please ask...and excuse my franker and spelling I wrote this on my Droid.

    Sent from my Droid using Tapatalk
  2. aristo1963
    Offline

    aristo1963 New Member

    Joined:
    Dec 6, 2009
    Messages:
    110
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Goldsboro,N.C.
    Worth a sticky imodancedroid
  3. gavron
    Offline

    gavron New Member

    Joined:
    Jan 29, 2010
    Messages:
    555
    Likes Received:
    0
    Trophy Points:
    0
    There was no brick here.

    E
  4. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    It was bricked...if you look at it from my point of view. If I would have brought it to the Verizon store they would have wanted to replace my wife's phone. My story's intentions was to let people know as follows; if your phone hangs up on the "m" screen after u install the official 2.2 froyo...you are not stuck...there is hope....you don't have to bring ur phone to the Verizon store with hopes of getting a replacement phone in 3 days *crosses fingers*....
    There is an alternative to going to the store. Use a user 2.2 rom that is rooted...that you can get the links off of this site...there are many and theater make ur phone run great ;)

    Sent from my Droid using Tapatalk
  5. gavron
    Offline

    gavron New Member

    Joined:
    Jan 29, 2010
    Messages:
    555
    Likes Received:
    0
    Trophy Points:
    0
    I don't want to split hairs with you, but here's what is clear.

    1. If you hadn't done something that's not recommended, NOTHING would have been wrong with the phone.

    2. Once you color outside those lines, you can't call it "bricked" unless you can't undo what you did.

    3. You did. You undid. It wasn't bricked.

    Real "brick"means SBF won't restore it either.

    Until then, it's a phone that doesn't like its ROM or kernel.

    E
  6. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    Lol...

    1. Maybe there is a misunderstanding. My wife's Droid got the official froyo update...when the phone rebooted it hung on the m screen. The only way it would reboot was to do a battery pull. So as far as me leaving the phone alone it would have had to go to Verizon. So rather than laying down in defeat I installed clockwork and put a rooted rom on the phone that worked.

    2. Google is a search engine do a search for; phone locked after official 2.2 froyo pushed to phone...the majority of people are bringing the phone to Verizon and getting a new phone. My story is an alternative...if you don't mind using an unofficial rom....which in my opinion are better than the factory rom.

    3. Do you want my user name and password to change my thread title from what it is too; bricked or not bricked...a love story?

    Serious...people on the forum boards can be so critical and anal about a simple person like me trying to give some help to peeps who may be frustrated b/c their phone is stuck on the m from an official "pushed" Froyo update.

    -maybe my story will help someone :)

    Sent from my Droid using Tapatalk
  7. xkape
    Offline

    xkape Premium Member Theme Developer Premium Member

    Joined:
    Jul 27, 2010
    Messages:
    3,876
    Likes Received:
    20
    Trophy Points:
    0
    Location:
    OH-IO
    It's not out of frustration. I don't think anyones trying to "argue" with you. I think they are trying to get the record strait for future users looking for help. All these threads will be here for awhile. While what you did is definately valuable information, it is not for someone looking for bricked phone help. However, the thread will reamina nd it will end up helping many people without your knowledge. Probably already has.
  8. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    Since your wife was installing the official 2.2 update, presumably her phone isn't rooted. How did you get your custom recovery on there? I'm not asking because I need to know how but in case there may be a lesson learned I can point out.
  9. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    A
    Well thanks for the response. I didn't mean to be mean or be a butt. I was just excited I found a solution and was not in the right state of mind.

    Sent from my DROiD PiNKMiX v2.0 using Tapatalk
  10. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    I put the phone in some mode holding the power button and the dpad up....which is towards the screen. I used a program called rsd lite to load a program called sprecovery on the phone. I rebooted the phone into sprecovery and turned phone into mass storage and loaded rom onto phone...then I installed the rom with sprecovery. All the programs mentioned above can be found from searches within this forum....hope that helps.


    Sent from my DROiD PiNKMiX v2.0 using Tapatalk
  11. SSHGuru
    Offline

    SSHGuru New Member

    Joined:
    Nov 23, 2009
    Messages:
    3,839
    Likes Received:
    30
    Trophy Points:
    0
    Location:
    Fort Lauderdale
    I think the term bricked doesn't have to mean permanent. I can mean screwed up to the point of almost tossing the phone in the garbage.

    I did that and it took me 8 hours to get the phone back to where it was. And I had to use RSD Light after searching for hours to get it back.

    Of course now I have three backups and titanium..
  12. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    Thanks for the reply. As I said prior, the purpose of my inquiry is to evaluate your procedure to look for issues. When you flashed SPRecovery, was it SPRecovery_ESE81.sbf?
  13. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    I think I have 2 backups lol....thanks for the post :)



    Sent from my DROiD PiNKMiX v2.0 using Tapatalk
  14. neo4uo
    Offline

    neo4uo New Member

    Joined:
    Jul 10, 2010
    Messages:
    11
    Likes Received:
    0
    Trophy Points:
    0
    Yes I used ese81

    Sent from my DROiD PiNKMiX v2.0 using Tapatalk
  15. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    I'm pretty sure that the most widely held understanding of the word "bricked" is one of permanence. If it's not permanent it's just hosed up and pending being put in the hands of someone who knows how to fix it. For me, there is no such thing as "unbricking". If it can be unbricked, then it wasn't bricked. If it can be unbricked, then it's not "as useless as a brick". A brick will never be a smartphone. If your device has any chance of being a smartphone again, it's not a brick.
  16. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    Cool. The way you did your steps the kernel mismatch of the flash vs. your phone probably didn't come into play too much (if at all). Even though you flashed an ESE81 kernel (that SPRecovery also contains the ESE81 kernel) onto a FRG01B phone, it doesn't sound like you ever let the OS attempt to boot after that and went straight to using SPRecovery to load a complete ROM update.zip which should have then replaced the kernel and everything else, cleaning things up.
Search tags for this page

brickear android 2.2

,

fix droid dna kernel brick

,

how to fix bricked n900

,

is my droid 2 bricked

,

repair droid 2 brick