Froyo Here For The Droid X

Discussion in 'Droid X Hacks' started by Shadez, Aug 20, 2010.

  1. biggestmexi

    biggestmexi Member

    Joined:
    Nov 5, 2009
    Messages:
    256
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0

    Is that the clockwork mod revocery your talking about or the bootstrapper?

    Anyway. If he made the app to modify the files in the first place, im sure there is a way to revert them with out SBF'ing your phone.

    He just has to do it.
     
  2. makaveliq3

    makaveliq3 Member

    Joined:
    Aug 20, 2010
    Messages:
    67
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Ok so since I ran koash's recovery I can't do this by the sound of things. I don't understand the .sdf thing so I'm not ready to do it. But i'm wondering though won't I have the same problem with the OTA update in a few weeks?

    If koash's recovery messed up being able to update, won't it prevent the offical OTA one too?
     
  3. Taurus

    Taurus Member

    Joined:
    Jan 8, 2010
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    way to get a head count increase at MDW, I will pass!
     
  4. uptheforest

    uptheforest Member

    Joined:
    Nov 4, 2009
    Messages:
    83
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Eutawville, SC
    Ratings:
    +0
    for people familiar with adb there is this floating around on alldroid for anyone who installed koush's recovery and dont want to reflash the sbf file

    With advice from drhill on androidforums I made these changes with root explorer

    Those with logwrapper problems. You don't need to reflash.

    You need to connect via adb and remount your system folder with rw permission.

    Go to /system/bin

    remove the hijack link to logwrapper and rename logwrapper.bin to logwrapper.

    I was extra safe and made a backup of hijack, logwrapper, and logwrapper.bin. Then I:
    rm logwrapper
    cp logwrapper.bin logwrapper

    Then exit adb.

    Currently flashing now.



    hope that helps
     
  5. just4747

    just4747 Member

    Joined:
    Jun 25, 2010
    Messages:
    430
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Can someone please PM me the SBF file to flash? Stupid koush recovery

    In /bin now...can you explain this part a little more please?: remove the hijack link to logwrapper and rename logwrapper.bin to logwrapper
     
  6. Taurus

    Taurus Member

    Joined:
    Jan 8, 2010
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    You can find the download link at the same place you downloaded the "stupid" Koush recovery.
     
  7. biggestmexi

    biggestmexi Member

    Joined:
    Nov 5, 2009
    Messages:
    256
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    link to follow to see if this works

    also, couldnt we do this via root explorer. seems like we could.
     
  8. jstuart83

    jstuart83 Member

    Joined:
    Aug 19, 2010
    Messages:
    30
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    holdup guys we were taking a chance installing that recovery its no ones fault but ourselves.
     
  9. GrillMouster

    GrillMouster Member

    Joined:
    Nov 23, 2009
    Messages:
    289
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Awesome stuff. I can't wait to see more people's accounts of how 2.2.6 is working for them.

    So, this is not a custom ROM, not a port from a dev phone, but a leaked version from Motorola. So, while it's not "official" (meaning it hasn't been released publicly by Motorola), it could very well wind up being the version that Motorola does release officially by OTA (with the exception of root, of course). Is that right? If the final version that Motorola releases via OTA is a more current version than this one, then it will have a different build number, right? And if that's correct, then we should be able to upgrade to the "official" version whenever it's released.

    If I decide to hold off on this update, and install the OTA, would I be unable to root until someone finds a way to root 2.2, or will I be able to SBF back to 2.1, then manually install the rooted 2.2?
     
  10. avt123

    avt123 Member

    Joined:
    Jan 28, 2010
    Messages:
    278
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I just deleted the hijack file, removed a permission from one logwrapper file and removed .bin from the other.... All using Root Explorer. I am currently "Unpacking new files" on the install.... I think it is working because it would fail much earlier than this... I will report back if it installs.
     
  11. uptheforest

    uptheforest Member

    Joined:
    Nov 4, 2009
    Messages:
    83
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Eutawville, SC
    Ratings:
    +0
    i just copied and pasted, so i didnt do this myself but would guess that you delete the hijack link and then simply rename the logwrapper file. sorry, i hate messing with adb and havent done it on the droid x yet. There is another user here trying it so i would suggest to wait and see if his efforts work out.
     
  12. biggestmexi

    biggestmexi Member

    Joined:
    Nov 5, 2009
    Messages:
    256
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I see in system/bin that there is:

    logwrapper
    19 aug blah blah rwxrwxrwx -> hijack ( so remove the permission from this file)

    and

    logwrapper.bin
    19 aug blah blah rwxr-xr-x (remove the .bin from this file)

    and then the hijack file should be deleted........aces.


    lol well then ^^^^^^
     
Search tags for this page

no su under xbin android