1. Download our Official Android App: Forums for Android!

Root 43v3r root not working on .893

Discussion in 'Android Devices' started by stoney bones, Dec 28, 2011.

  1. stoney bones

    stoney bones Member
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    50
    Joined:
    Dec 15, 2011

    Dec 15, 2011
    50
    2
    16
    *
    * and set USB Mode to Charge Only
    *
    * READY TO ROOT YOUR DROID BIONIC WHEN YOU ARE!
    Press any key to continue . . .
    "* Running zergRush exploit..."
    1607 KB/s (23052 bytes in 0.014s)

    [**] Zerg rush - Android 2.2/2.3 local root
    [**] (C) 2011 Revolutionary. All rights reserved.

    [**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

    [+] Found a GingerBread ! 0x00016118
    [*] Scooting ...
    [*] Sending 149 zerglings ...
    [*] Sending 189 zerglings ...
    [+] Zerglings found a way to enter ! 0x18
    [+] Overseer found a path ! 0x000161e0
    [*] Sending 189 zerglings ...
    [+] Zerglings caused crash (good news): 0x40122c5c 0x0074
    [*] Researching Metabolic Boost ...
    [+] Speedlings on the go ! 0xafd25ac9 0xafd39877
    [*] Sending 185 zerglings ...

    [-] Bad luck, our rush did not succeed :(
    * Wait about 30 seconds for the adb server to restart as root
    Press any key to continue . . .
    * Installing busybox, su, and SuperUser apk...
    remount failed: Operation not permitted
    failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
    failed to copy 'su' to '/system/xbin/su': Read-only file system
    3860 KB/s (754980 bytes in 0.191s)
    pkg: /data/local/tmp/Superuser.apk
    Failure [INSTALL_FAILED_ALREADY_EXISTS]
    Unable to chmod /system/xbin/su: No such file or directory
    Unable to chmod /system/xbin/busybox: No such file or directory
    /system/xbin/busybox: not found
    link failed Read-only file system
    Unable to chmod /data: Operation not permitted
    * Installing 43V3R Root...
    failed to copy 'mount_ext3.sh' to '/system/bin/mount_ext3.sh': Read-only file system
    Unable to chmod /system/bin/mount_ext3.sh: Read-only file system




    i just got a new bionic, did the latest OTA update that was pushed to me....then tried 43v3r root, option 2 and this is the result every time. any ideas?
     

    Advertisement

  2. JrzDroid

    JrzDroid Android Expert
    Rank:
    None
    Points:
    163
    Posts:
    1,682
    Joined:
    Nov 30, 2009

    Nov 30, 2009
    1,682
    308
    163
    T-Mobile
    NJ
    I'm having the exact same issue
     
  3. kingofdarkness

    Rank:
    None
    Points:
    25
    Posts:
    9
    Joined:
    Dec 26, 2011

    Dec 26, 2011
    9
    0
    25
    Kansas
    Try option 1. It removes the updates and reverts it back to original system version, which should then root without any problem. After you continue through the process of 43V3R rooting your phone you can update to the latest version and maintain root. I also had to use option 1 after the OTA broke my original root.
     
  4. WA_Bob

    WA_Bob Android Expert
    Rank:
    None
    Points:
    103
    Posts:
    799
    Joined:
    Apr 11, 2011

    Apr 11, 2011
    799
    109
    103
    Male
    Forester
    West edge of the East Texas Piney Woods

    I didn't get a new Bionic, but I did manage to brick my old one. When I used this to bring it back to life, I took the OTA before rooting and found it wouldn't root the OTA. This same method got me back on root!
     
  5. stoney bones

    stoney bones Member
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    50
    Joined:
    Dec 15, 2011

    Dec 15, 2011
    50
    2
    16


    i tried option 1. it says if you see the prompt that says "waiting for device" install said drivers...i installed said drivers, did a soft reset, but still hangs up on "waiting for device" with no luck.
     
  6. stoney bones

    stoney bones Member
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    50
    Joined:
    Dec 15, 2011

    Dec 15, 2011
    50
    2
    16
    i found my error.

    its says to hol vol up, vol down, and pwr button to soft reset and go into ap fast boot mode.

    i would hold the buttons, wait, then the screen would go black so i released the buttons and it would restart...

    upon restarting i was curious how to tell if you were in ap fast boot mode.....well after some tinkering i realized you must keep holding all three buttons even after the screen goes blank and wait for the boot menu to actually get to the fast boot mode.


    duuuuuh. wish that was explained earlier...pretty frustrating oversight there. but, now re-imaged to the 886 with root and i will now attempt .893 and see if root maintains as advertised.

    thanks for the info
     
  7. bryangaskill

    bryangaskill Lurker
    Rank:
    None
    Points:
    5
    Posts:
    1
    Joined:
    Feb 9, 2012

    Feb 9, 2012
    1
    0
    5
    I am in a jam also could you please send me the 4ever root link too my speakerphone went out got a new one but now i cant root thanks in advance.
     
  8. OutOfPhase

    OutOfPhase Premium Member
    Rank:
    None
    Points:
    523
    Posts:
    4,024
    Joined:
    Dec 7, 2010

    Dec 7, 2010
    4,024
    2,149
    523
    Retired Lineman
    Tampa, FL
    I am uploading in now. I will send you a link in a minute.
     

Share This Page

Loading...