I screwed up, and created a Frankenstein monster...


Last Updated:

  1. icmedia

    icmedia New Member This Topic's Starter

    Joined:
    Jul 24, 2010
    Messages:
    3
    Likes Received:
    0
    OK, so here's what I did, starting off with a rooted DX from which I had removed a bunch of bloat:

    1. Loaded the startup.zip file found at MyDroidWorld onto my SD Card
    1. Used SBF to get my phone back to a stock state
    2. Moved my su file from /bin to /xbin
    3. Rebooted into recovery mode
    4. Selected apply sdcard:update.zip
    5. Rebooted to a glorious, wonderful 2.2---with root access.

    Now, here's where I screwed things up-In my haste to remove the bloat again, I accidentally removed the Dialer module. Yeah, a BIG whoops. I immediately lost service, along with my ability to use any of the Dialer-associated functions. I tried to restore it using Titanium Backup (I backed everything up before uninstalling programs), to no avail...so, in a panic, I ran the SBF again, which really freaked me out, because it caused my phone to go into a Droid-Eye bootloop. FML. However, I was able to once again reboot into recovery mode, and applied update.zip again, and the phone started back up! But, with a few really troubling issues:

    1. I have no lockscreen, nor the ability to enable a regular lockscreen in Settings.
    2. The camera button no longer pulls up anything.
    3. The home button works, but not fully; I can't pull up a "Recently Used" menu, nor will it exit out of any programs back to my homescreen.
    4. Several programs no longer function, such as VZ Navigator, PayPal, and Calorie Counter (and I haven't checked all of them yet but I'm sure there are more).
    5. I LOST ROOT :(
    6. I no longer have Flash in my browser

    It seems as if, through my infinite n00bness, I have created a slightly less functional hybrid monster combination of 2.1 and 2.2. My efforts to try SBF and different versions of the startup.zip file (both the rooted and non-rooted versions from the Droid X Forums) have done nothing.

    Does anyone here have any idea how to fix this (or even what I've done)? Other than those issues, I have full calling/texting/email/browsing capabilities on my ohone, but it just isn't the same. I know I should have left well enough alone, but now that I haven't, is there any hope for me?
     

    Advertisement
  2. geno51

    geno51 Well-Known Member

    Joined:
    Jul 11, 2010
    Messages:
    48
    Likes Received:
    7
    Dude wow!!!
     
  3. deadinside

    deadinside Well-Known Member

    Joined:
    Jul 24, 2010
    Messages:
    124
    Likes Received:
    23
    This is why you should always use adb pull to pull your apps folder to your pc, before removing the system apk's.

    Other than that I am not sure if your issue can be fixed.
     
  4. JubbaTheHutt

    JubbaTheHutt Well-Known Member

    Joined:
    Jul 7, 2010
    Messages:
    998
    Likes Received:
    103
    There, I fixed it for ya :D
     
    urdaddi likes this.
  5. tiWonggg

    tiWonggg Member

    Joined:
    Jul 31, 2010
    Messages:
    17
    Likes Received:
    2
    Go into recovery mode, wipe data/factory rest and wipe cache partition, flash back to 2.1 using sbf again, and start over.
     
    Foxgguy2001 likes this.
  6. jbhumph

    jbhumph Well-Known Member

    Joined:
    Jul 4, 2010
    Messages:
    652
    Likes Received:
    54
    Yeah, I would think a hard reset/recovery mode would take you back, yes? No?
     
  7. deadinside

    deadinside Well-Known Member

    Joined:
    Jul 24, 2010
    Messages:
    124
    Likes Received:
    23
    Nah, I would not have said that.

    The real problem is no dialer + no singal = No OTA to save him on this. At this current point in time I would imagine he has the most expensive paperweight known to man.
     
  8. Hrethgir

    Hrethgir Well-Known Member

    Joined:
    Feb 16, 2010
    Messages:
    1,684
    Likes Received:
    225

    No, he got the dialer part fixed:

    So when the official OTA Froyo update comes out, he should be able to get that, no?
     
  9. icmedia

    icmedia New Member This Topic's Starter

    Joined:
    Jul 24, 2010
    Messages:
    3
    Likes Received:
    0
    It looks like I was able to salvage things, using the following method:

    1. Run SBF again
    2. Boot into recovery mode
    3. Wipe user data/restore factory settings
    4. Root using one-click method
    5. Restore all programs and settings with Titanium Backup
    5. Move su file from /bin to /xbin
    6. Boot into recovery mode
    7. Run setup.exe
    8. Boot into a fully functional, loaded 2.2 with root access

    Thanks to the fine folks at MyDroidWorld.com for the suggestions to make this work! Looks like no matter how bad you screw up, there is still hope!
     
  10. sund0wn

    sund0wn Well-Known Member

    Joined:
    Aug 10, 2010
    Messages:
    775
    Likes Received:
    175

    +1,661,213 (the number of times it's been posted in this forum alone)

    wipe data/cache before flashing sbf. always.
     
    Foxgguy2001 likes this.

Share This Page

Loading...