Welp its stuck at the Motorola Logo after 2.2 Update...


Last Updated:

  1. GTPprix

    GTPprix Well-Known Member This Topic's Starter

    Joined:
    Apr 27, 2010
    Messages:
    62
    Likes Received:
    1
    I just finished updating my wifes Droid X to 2.2 (rooted) moved SU etc.. the phone boots completely (I can ADB in and it makes noise) however it only shows the M logo. I cant boot into recovery and the only way to make it boot is to adb reboot-bootloader anyone know WTF is going on here? I've never seen anything like this before!
     

    Advertisement
  2. Araldo

    Araldo Well-Known Member

    Joined:
    Jun 5, 2010
    Messages:
    73
    Likes Received:
    2
    reflash with SBF
     
  3. GTPprix

    GTPprix Well-Known Member This Topic's Starter

    Joined:
    Apr 27, 2010
    Messages:
    62
    Likes Received:
    1
    downloading right now, hopefully that does the trick but I really wish I knew what caused it. Everything installed fine with no errors etc.
     
  4. cmathis

    cmathis Well-Known Member

    Joined:
    Apr 8, 2010
    Messages:
    90
    Likes Received:
    1
    Same here. I even flashed the SBF and then tried the update again (AFTER redownloading it) with the phone completely stock, and I STILL got stuck at the MOTO screen. Ugh... I really want Froyo!!! Help anyone?
     
  5. D13

    D13 Well-Known Member

    Joined:
    May 28, 2010
    Messages:
    2,088
    Likes Received:
    234
    try wiping data/cache first
    then flash the sbf
    then reroot with universalandroot
    move su to xbin
    wipe data/cache
    install update
     
  6. GTPprix

    GTPprix Well-Known Member This Topic's Starter

    Joined:
    Apr 27, 2010
    Messages:
    62
    Likes Received:
    1
    Now one thing I DID find that may help others in the future is I was able to boot the phone using adb reboot bootloader even though it didnt go to the bootloader but actually into a regular startup, is this of use to anyone?
     
  7. GTPprix

    GTPprix Well-Known Member This Topic's Starter

    Joined:
    Apr 27, 2010
    Messages:
    62
    Likes Received:
    1
    Ok so hopefully no one else experiences this however I WAS able to get everything working but only AFTER I did a wipe all user data, the cache for whatever reason had no bearing. I could load the sbf and be right back at same issue but only until I hit the clear all user data :)
     
  8. arlan_jacob

    arlan_jacob New Member

    Joined:
    Sep 1, 2010
    Messages:
    2
    Likes Received:
    0
    I had this same problem 6 times then i foung the phone was working you just have to remove the battery for at least 4 min after turning it off or reseting it every time sucks but it is a work around.
     
  9. philipwelch4

    philipwelch4 Member

    Joined:
    Jun 10, 2010
    Messages:
    14
    Likes Received:
    0
    Okay, hopefully someone can help here.

    A buddy of mine got his X on Tuesday, today I used "universalandroot" from stock 2.1 to obtain root. I confirmed he had root using a terminal emulator and using ADB (my Windows 7 64-bit has recognized his phone throughout this entire process). From rooted 2.1, I used ADB to move SU to xbin, and all worked well. I installed the 2.2 update.zip from here and it booted and I had root.

    From there I installed the Droid X Recovery Bootstrap, it asked for SU permissions and I allowed. I then attempted to reboot into recovery (I now believe I should have ran Rom Manager at this point so it could update the Bootstrap..but I didn't) and the device hung at the M logo for about 10 minutes. I pulled the battery from here and the phone continued to stay at the M logo.

    From here I successfully SBF'd the device back to stock 2.1, re-rooted, and applied the 2.2 update, forgetting to move SU to xbin. As expected, the phone didn't get past the M logo.

    I SBF'd again, re-rooted, moved the SU, went into recovery and wiped data/cache, booted back to 2.1 and confirmed we still had SU, went back to recovery and flashed the 2.2 update.zip. It is still hung at the M logo.

    The entire time this has been hung at the M logo, we have heard the "Droid" standard notification as if the phone has started, can turn the volume up/down, unlock the screen, even turn the phone off by pressing the power button and hitting the screen where the "Power Off" option is in the menu. We also tried leaving the battery out for about 5 minutes.

    The phone is accessible via ADB, has SU access, can reboot into recovery (have successfully done it using ADB, still shows M logo, but pressed the search button to bring up recovery options, scrolled down to the 4th option and pressed the camera button, waited a minute then pressed the camera button again as if selecting "reboot system now" and the system reboots with the M logo and can unlock the screen, etc.)

    We are now SBFing for the 4th time, and are going to re-root and call it a night and hope for some help from this forum. If anyone has this figured out I would seriously appreciate the help. Even alternate methods of getting to 2.2 would be appreciated (using Rom Manager, etc).

    Thanks in advance!
     
  10. D13

    D13 Well-Known Member

    Joined:
    May 28, 2010
    Messages:
    2,088
    Likes Received:
    234
    easy wasy

    1. root
    droid x bootstrap, make sure you have the updated version and press bootstrap 2. at the top
    3. download rom manager, press flash clockwork at the top
    4. download 2.2 from there
    5. choose back-up in rom pre-installation
    6.done:D
     
  11. GTPprix

    GTPprix Well-Known Member This Topic's Starter

    Joined:
    Apr 27, 2010
    Messages:
    62
    Likes Received:
    1
    Just to bring this back to the top, it did the SAME thing with the official 2.2 update, I've got a jacked phone!
     
  12. kushineris

    kushineris Well-Known Member

    Joined:
    May 15, 2010
    Messages:
    55
    Likes Received:
    2
    i sbfed back to stock 2.1 from root, then after i installed the update it was stuck on the m logo. Freaked out went into verizon new phone will be here tomorrow. Well i was able to finally get it into recovery and wiped the cache partition. Guess i just forgot a step. Should i take the new phone or stick with my old one now. Everything seems to be working gogod so far. I guess only the day will tell since it will be here tomorrow.
     

Share This Page

Loading...