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

Thread Status:
Not open for further replies.

Root warning! be careful with the 2.11.605.9 OTA

Discussion in 'Android Devices' started by scotty85, Dec 18, 2011.

  1. scotty85

    scotty85 Android Expert
    Thread Starter
    Rank:
    None
    Points:
    1,413
    Posts:
    11,139
    Joined:
    Jul 25, 2010

    Jul 25, 2010
    11,139
    7,418
    1,413
    *this stickys days are numbered. i will unstick this,and modify the root/unroot thread soon, as it prolly doesnt really need to be here any longer*

    -if you accidently take the OTA,or get a phone with 2.11.605.9,its not as big a deal as it first appeared to be. you can roll back to 2.11.605.5 simply by running an RUU in the form of a .exe or PG05IMG file.

    -you can also HTCdev unlock,if you have no warranty. once youve unlocked,you can flash a recovery,flash a rooted stock 2.11.605.5 rom,and run revolutionary to achieve s-off
    __________________________________________________________________________________


    DO NOT attempt to take the 2.11.605.9 OTA unless you have allready run revolutionary,or rooted old school and are running shadowmites permanent hboot.

    accidentally taking the OTA with the old 1.04.2000 eng hboot,will break root,and possibly take away your s-off hboot.

    the zergRush exploit appears to have been patched in this update. :mad:

    Code (Text):
    1.  =============================================
    2. | Revolutionary S-OFF & Recovery Tool 0.4pre4 |
    3.  =============================================
    4.     Brought to you by AlphaRev & unrEVOked.
    5.  
    6. Waiting for device...
    7. Found your device: ADR6400L (mecha-1.05.0000, Android: 2.3.4, ROM version: 2.11.
    8. 605.9)
    9.  
    10. This is a beta release and requires a beta release key.
    11. Please visit: http://revolutionary.io for more information.
    12.  
    13. Enter beta key [ serial: HT12CS012936 ]: DW5t1qMsVk8GiPEu
    14. Beta key accepted - thank you for participating!
    15.  
    16. Zerging Root... this might take a minute or so.. Failed to get Root! :(
    17. Press (almost) any key to exit.
    tried to run zergRush manually:

    Code (Text):
    1. c:\tbolt>[COLOR="Red"]adb push zergRush /data/local/[/COLOR]
    2. 1185 KB/s (23060 bytes in 0.019s)
    3.  
    4. c:\tbolt>[COLOR="red"]adb shell[/COLOR]
    5. $ [COLOR="red"]chmod 755 /data/local/zergRush[/COLOR]
    6. chmod 755 /data/local/zergRush
    7. $ [COLOR="red"]/data/local/zergRush[/COLOR]
    8. /data/local/zergRush
    9.  
    10. [**] Zerg rush - Android 2.2/2.3 local root
    11. [**] (C) 2011 Revolutionary. All rights reserved.
    12.  
    13. [**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
    14.  
    15. [+] Found a GingerBread ! 0x00000118
    16. [*] Scooting ...
    17. [*] Sending 149 zerglings ...
    18. [*] Sending 189 zerglings ...
    19. [-] Hellions with BLUE flames ! [COLOR="Blue"]<--yikes![/COLOR]
    20. $
    see this thread for discussion: http://androidforums.com/thunderbol...-revolutionary-work-new-update-installed.html
     

    Advertisement

    Yeahha and Jerniganc like this.
  2. Yeahha

    Yeahha Usually off topic
    Rank:
    None
    Points:
    813
    Posts:
    10,472
    Joined:
    Jul 29, 2010

    Jul 29, 2010
    10,472
    4,693
    813
    ...
    FG
    If you are rooted and on stock you may want to flash the roms linked in this post http://androidforums.com/thunderbol...-rooted-ota-2-11-605-9-files.html#post3685414

    Big thanks to Jrocker23 who has posted both stock rooted and stock debloat roms. This will prevent you from getting the OTA.

    If you do not wish to flash the rom then you should flash this recovery in hboot to allow your phone to accept the update, you will lose root access as a result of the update.

    GB 2.11.605.5(official OTA): Multiupload.com - upload your files to multiple file hosting sites!
    md5: 7b25c652cbe1422860eb132709895644

    If you rooted and on a custom recovery the update will fail and soft brick your phone.

    If this happens you will need to wipe cache and dalvik cache in recovery and you will be able to reboot again. For more info on accidently accepting the OTA check this thread http://androidforums.com/thunderbol...-help-w-automatic-ota-update.html#post3686026
     

Share This Page

Loading...