1. 2015 is going to be a great year for Android! Why wait??
    Samsung Galaxy Note 5 | Samsung Galaxy S6 | HTC One M9
  2. New Forum Created: Samsung Gear VR!

Thunderbolt Root/Unroot Thread


  1. scotty85

    scotty85 Guides Guide

    this thread is dedicated to the current known methods of rooting the thunderbolt.

    i will do my best to change this post as these methods are modified or become outdated,and keep the best,current methods here.

    after root see the Thunderbolt ROM list for a list of roms,kernels and mods :cool:

    for some extra info and "how to"s of rooting see http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html

    if youre reading this and considering rooting your device,a word of warning:
    DO NOT ever attempt to accept an OTA while rooted and running a custom recovery.
    an official OTA update needs the stock recovery to apply it. attempting to take an OTA without the stock recovery can result in a failed harmless attempt,a fixable bootloop,or even a brick. so please... dont do it.

    and now,on with the info. enjoy :)


    Revolutionary
    a new method has just become available that does not wipe your data. this is 100% the best,and most reccomended way to root your thunderbolt at this time.

    see this page for info:
    Revolutionary

    and a video from nate mills:
    How to Root - HTC Thunderbolt (No Data Wipe! Newest & Fastest) - YouTube

    special note: the minor OTA to firmware number 2.11.605.9 patches the exploit used by revolutionary. there are 2 options:
    1)several users have reported being able to downgrade to 2.11.605.5 simply by running an RUU for that firmware,despite an s-on hboot wich would normally prevent you from going backwards in version numbers. PG05IMG and .EXE files for this version are available in post 4. (needs verified)
    *please note that downgrading WILL wipe your personal data
    2) achieve temp root via another means,then run revolutionary(this method follows)

    feel free to do wichever is most comfortable :)

    following is how to manually temp root and run revolutionary. i am happy to keep supporting this for those that wish to do it.

    however,there is now a very good tool to do this for you:
    http://androidforums.com/thunderbolt-all-things-root/563593-all-in-one-htc-thunderbolt-tool.html
    it will root and unroot your thunderbolt.
    this is not my work,so please post questions about it in that thread,where we will do our best to help you :)

    __________________________________________________________________________________
    how to manually root 2.11.605.9/2.11.605.19 WITHOUT downgrading

    as usual,i take no credit- i just put it together :)
    credits:
    -jelly doughnut for pointing me to this thread,and the Desire HD guys for this thread.
    *make sure you thank jelly in this post
    -sele and crew at HTC Thunderbolt Forum for what i like to call the "mini adb" concept

    1)download miniadb_tbolt2.zip from here: mini-adb_tbolt2.zip
    md5: ef01f616471673d3eeb71b4cac4b8118
    download and install these modified htc drivers

    2)set up adb:
    -extract miniadb_tbolt2.zip and place the unzipped folder onto the root of your C\ drive on your PC
    -open a command window. windows 7,click on start bubble,type "command" in the search box. a small black window should open up

    3)download DHD Downgrade folder

    4)open the DHDDowngrade.zip file,then the folder contained inside of it. transfer "Fre3vo" into the tbolt2 folder with adb/fastboot.(ignore the rest of the files in DHDDongrade,fre3vo is the only one you need)

    5)in your command window: change to the tbolt2 directory by typing:
    cd c:\mini-adb_tbolt2 (your promt should change to c:\mini-adb_tbolt2>)
    *note that in the next few steps,anything in bold type is an adb command. you can directly copy from this window,and paste into your command window to eliminate typos.

    6)enable usb debugging,plug in your phone via usb. select "charge only" mode.

    7)make sure adb is seeing your phone:
    adb devices (should return your serial number)

    8) enter the commands from your link,one at a time,hit enter after each:

    adb push fre3vo /data/local/tmp

    adb shell chmod 777 /data/local/tmp/fre3vo

    adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF


    9)make sure it worked. when you see "exploiting device" then your command prompt again:
    adb shell (if your prompt changes to a # youre good to go)

    10)run revolutionary again. this time it will work really fast. you can have it install clockwork if you wish to use that recovery.

    10)flash the superuser 3.07 files linked on revolutionarys info page

    youre done :D


    heres what youll see in the command window(red are my inputs,blue are just additional comments):
    Code (Text):
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Scott>[COLOR="Red"]cd c:\tbolt2[/COLOR]

    c:\tbolt2>[COLOR="Red"]adb devices[/COLOR]
    * daemon not running. starting it now *
    * daemon started successfully *
    List of devices attached
    HTxxxxxx    device


    c:\tbolt2>[COLOR="red"]adb push fre3vo /data/local/tmp[/COLOR]
    956 KB/s (9796 bytes in 0.010s)

    c:\tbolt2>[COLOR="red"]adb shell chmod 777 /data/local/tmp/fre3vo[/COLOR]

    c:\tbolt2>[COLOR="red"]adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF[/COLOR]
    fre3vo by #teamwin
    Please wait...
    Attempting to modify ro.secure property...
    fb_fix_screeninfo:
      id: msmfb
      smem_start: 802160640
      smem_len: 3145728
      type: 0
      type_aux: 0
      visual: 2
      xpanstep: 0
      ypanstep: 1
      line_length: 1920
      mmio_start: 0
      accel: 0
    fb_var_screeninfo:
      xres: 480
      yres: 800
      xres_virtual: 480
      yres_virtual: 1600
      xoffset: 0
      yoffset: 0
      bits_per_pixel: 32
      activate: 16
      height: 94
      width: 56
      rotate: 0
      grayscale: 0
      nonstd: 0
      accel_flags: 0
      pixclock: 0
      left_margin: 0
      right_margin: 0
      upper_margin: 0
      lower_margin: 0
      hsync_len: 0
      vsync_len: 0
      sync: 0
      vmode: 0
    Buffer offset:      00000000
    Buffer size:        8192
    Scanning region f0000000...
    Scanning region f00f0000...
    Scanning region f01e0000...
    Scanning region f02d0000...
    Scanning region f03c0000...
    Scanning region f04b0000...
    Scanning region f05a0000...
    Scanning region f0690000...
    Scanning region f0780000...
    Scanning region f0870000...
    Scanning region f0960000...
    Scanning region f0a50000...
    Scanning region f0b40000...
    Scanning region f0c30000...
    Scanning region f0d20000...
    Scanning region f0e10000...
    Scanning region f0f00000...
    Scanning region f0ff0000...
    Scanning region f10e0000...
    Scanning region f11d0000...
    Scanning region f12c0000...
    Scanning region f13b0000...
    Scanning region f14a0000...
    Scanning region f1590000...
    Scanning region f1680000...
    Scanning region f1770000...
    Scanning region f1860000...
    Scanning region f1950000...
    Scanning region f1a40000...
    Scanning region f1b30000...
    Scanning region f1c20000...
    Scanning region f1d10000...
    Scanning region f1e00000...
    Scanning region f1ef0000...
    Scanning region f1fe0000...
    Scanning region f20d0000...
    Scanning region f21c0000...
    Scanning region f22b0000...
    Scanning region f23a0000...
    Scanning region f2490000...
    Scanning region f2580000...
    Scanning region f2670000...
    Scanning region f2760000...
    Scanning region f2850000...
    Scanning region f2940000...
    Scanning region f2a30000...
    Scanning region f2b20000...
    Scanning region f2c10000...
    Scanning region f2d00000...
    Scanning region f2df0000...
    Scanning region f2ee0000...
    Scanning region f2fd0000...
    Scanning region f30c0000...
    Scanning region f31b0000...
    Scanning region f32a0000...
    Scanning region f3390000...
    Scanning region f3480000...
    Scanning region f3570000...
    Scanning region f3660000...
    Scanning region f3750000...
    Scanning region f3840000...
    Scanning region f3930000...
    Scanning region f3a20000...
    Scanning region f3b10000...
    Scanning region f3c00000...
    Scanning region f3cf0000...
    Scanning region f3de0000...
    Scanning region f3ed0000...
    Scanning region f3fc0000...
    Scanning region f40b0000...
    Scanning region f41a0000...
    Scanning region f4290000...
    Scanning region f4380000...
    Scanning region f4470000...
    Scanning region f4560000...
    Scanning region f4650000...
    Scanning region f4740000...
    Scanning region f4830000...
    Scanning region f4920000...
    Scanning region f4a10000...
    Scanning region f4b00000...
    Scanning region f4bf0000...
    Scanning region f4ce0000...
    Scanning region f4dd0000...
    Scanning region f4ec0000...
    Scanning region f4fb0000...
    Scanning region f50a0000...
    Scanning region f5190000...
    Scanning region f5280000...
    Scanning region f5370000...
    Scanning region f5460000...
    Scanning region f5550000...
    Scanning region f5640000...
    Scanning region f5730000...
    Scanning region f5820000...
    Scanning region f5910000...
    Scanning region f5a00000...
    Scanning region f5af0000...
    Scanning region f5be0000...
    Scanning region f5cd0000...
    Scanning region f5dc0000...
    Scanning region f5eb0000...
    Scanning region f5fa0000...
    Scanning region f6090000...
    Scanning region f6180000...
    Scanning region f6270000...
    Scanning region f6360000...
    Scanning region f6450000...
    Scanning region f6540000...
    Scanning region f6630000...
    Scanning region f6720000...
    Scanning region f6810000...
    Scanning region f6900000...
    Scanning region f69f0000...
    Scanning region f6ae0000...
    Scanning region f6bd0000...
    Scanning region f6cc0000...
    Scanning region f6db0000...
    Scanning region f6ea0000...
    Scanning region f6f90000...
    Scanning region f7080000...
    Scanning region f7170000...
    Scanning region f7260000...
    Scanning region f7350000...
    Scanning region f7440000...
    Scanning region f7530000...
    Scanning region f7620000...
    Scanning region f7710000...
    Scanning region f7800000...
    Scanning region f78f0000...
    Scanning region f79e0000...
    Scanning region f7ad0000...
    Scanning region f7bc0000...
    Scanning region f7cb0000...
    Scanning region f7da0000...
    Scanning region f7e90000...
    Scanning region f7f80000...
    Scanning region f8070000...
    Scanning region f8160000...
    Scanning region f8250000...
    Scanning region f8340000...
    Scanning region f8430000...
    Scanning region f8520000...
    Scanning region f8610000...
    Scanning region f8700000...
    Scanning region f87f0000...
    Scanning region f88e0000...
    Scanning region f89d0000...
    Scanning region f8ac0000...
    Scanning region f8bb0000...
    Scanning region f8ca0000...
    Scanning region f8d90000...
    Scanning region f8e80000...
    Scanning region f8f70000...
    Scanning region f9060000...
    Scanning region f9150000...
    Scanning region f9240000...
    Scanning region f9330000...
    Scanning region f9420000...
    Scanning region f9510000...
    Scanning region f9600000...
    Scanning region f96f0000...
    Scanning region f97e0000...
    Scanning region f98d0000...
    Scanning region f99c0000...
    Scanning region f9ab0000...
    Scanning region f9ba0000...
    Scanning region f9c90000...
    Scanning region f9d80000...
    Scanning region f9e70000...
    Scanning region f9f60000...
    Potential exploit area found at address f9fd6200:e00.
    Exploiting device...

    c:\tbolt2>[COLOR="red"]adb shell[/COLOR]
    # [COLOR="Blue"]<-indicates that you have temp root access[/COLOR]
     
    __________________________________________________________________________________
    how to unroot
    the revolutionary method of rooting uses a sneeky hboot exploit,and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. it not only gives you all the same fashboot flash abilities as the original engineering bootloader,but it very effectively blocks other hboots for overwriting it. its good,as you will remain s-off if you accidentally flash a full RUU,or accept an OTA,but makes it a little trickier to remove.

    for the time being, removal requires ADB to be set up and running and some commands entered in "fastboot" to to allow the permanent hboot to be overwritten. once an "s-on" tool is release,ill take th is part of this guide down.

    if you rooted the old skool manual way and have adb setup and working,you can use this guide to remove the permanent hboot.

    with Revolutionary,will come a new wave of rooters that have no clue what adb,or fastboot even are. for you folks, Sele and the crew in the "rescue sguad" at HTC Thunderbolt Forum have come up with a really clever way to get the adb basics,and the eng bootloader to flash,with minimal setup and confusion. with their permission,im borrowing it for our guide here.

    *WARNING* no siginture or file checks will be done flashing the new bootloader in hboot or fastboot.fastboot will literally flash "lets golf" as a bootloader if you tell it to. DO NOT mess with your hboot unless absolutely neccessary to return to stock for warranty purposes. if youre just tired of being rooted,flash the gingerbread ruu to get back to unrooted firmware and factory recovery. leaving the revolutionary s-off bootloader in place is the safest,and best option,and will not affect your ability to recieve OTAs.

    *AGAIN- if youre just following this procedure because youre tired of being rooted,skip this next section and leave the permanent hboot in place. jump to "Putting current stock firmware and s-on back onto the phone" and flash only the first "PG05IMG_no_hboot_2.11.605.9" file(you can flash the 2nd file too if you want,but the permanent hboot will block it ;))

    Setting up adb and removing the permanent hboot if youve never used adb before
    1)if you no longer have the htc drivers that you installed when rooting with revolutionary,download them again from here on revolutionarys website.
    2)next download *link removed (mirror)to somewhere convenient that youll be able to find it,like your desktop,or a "downloads" folder. it contains the old eng 1.40.2000 s-off hboot,and the bare minumum tools to install it.
    3)the following directions were using windows 7 and chrome browser. other OS may be slightly different-the end result is you want unzipped,inside tbolt folder to be on the root of your C: drive.
    -find the tbolt.zipdownload
    -click on tbolt.zip download and open it.
    -inside tbolt.zip,there is a folder labled tbolt. drag it to the root of C:. inside tbolt is the unpermanent hboot and some adb tools.
    4) charge your Thunderbolt to 100%
    5)click on then "start" bubble in the lower left corner of your screen. type "command" in the search window and hit enter. this will open a small black command window.
    6)enter the following command(by typing or copy/paste):
    Code (Text):
    cd c:\tbolt
    you should see your promt in the window change to: c:\tbolt>
    7)enter the follwing command:
    Code (Text):
    md5sums hbooteng.nb0
    check the output on the command window. THIS IS VERY IMPORTANT. the command must equal exactly 6991368ee2deaf182048a3ed9d3c0fcb if it does not,STOP!. delete the tbolt.zip download,and the unzipped tbolt folder from C:,re download and try it again. again,do not procede if the output in your command number does not equal it exactly.
    8)once the number matches,you can continue. copy and paste the following codes into the command window:
    Code (Text):
    adb devices
    the output should be your phones serial number

    now enter:
    Code (Text):
    adb reboot bootloader
    this will cause your phone to boot into FASTBOOT mode,wich is a white screen with colored letters.

    now enter:
    Code (Text):
    fastboot devices
    the result again,should be your phones serial number.

    9) now youre ready to enter the command to unlock the permanent hboot and flash the new,non permanent one.
    to unlock,enter:
    Code (Text):
    fastboot oem mw 8d08ac54 1 31302E30
    write the new hboot:
    Code (Text):
    fastboot flash hboot hbooteng.nb0
    if you select bootloader at this point from the fastboot menu, youll still see the permanent s-off hboot,so select reboot with the volume rocker and power button and let the phone reboot. after it boots,you can adb reboot bootloader again,or power off, then power on/vol down and check that your pink "UNLOCKED" or "REVOLUTIONARY" is gone and you have the old 1.49.2000 bootloader.

    here is what you should see in the command window,the red are my inputs:
    Code (Text):
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Scott>[COLOR="Red"]cd c:\tbolt[/COLOR]

    c:\tbolt>[COLOR="red"]md5sums hbooteng.nb0[/COLOR]

    MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
    Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
    Type md5sums -h for help

    [Path] / filename                              MD5 sum
    -------------------------------------------------------------------------------
    [c:\tbolt\]
    hbooteng.nb0                                   6991368ee2deaf182048a3ed9d3c0fcb

    c:\tbolt>[COLOR="red"][COLOR="red"]adb devices[/COLOR][/COLOR]
    * daemon not running. starting it now *
    * daemon started successfully *
    List of devices attached
    HT126S005970    device


    c:\tbolt>[COLOR="red"]adb reboot bootloader[/COLOR]

    c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
    HT126S005970    fastboot
    c:\tbolt>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
    ...
    OKAY [  0.006s]
    finished. total time: 0.006s

    c:\tbolt>[COLOR="red"]fastboot flash hboot hbooteng.nb0[/COLOR]
    sending 'hboot' (1024 KB)...
    OKAY [  0.183s]
    writing 'hboot'...
    OKAY [  0.219s]
    finished. total time: 0.403s

    c:\tbolt>
     
    Putting current stock firmware and s-on back onto the phone

    after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
    1)PG05IMG_no_hboot_2.11.605.19
    mirror: https://rapidshare.com/files/271867813/PG05IMG_no_hboot_2.11.605.19.zip
    md5: 334909756073760b3d7316e51a4ce837
    2)*link removed PG05IMG_hboot_ONLY_2.11.605.19.zip
    mirror:PG05IMG_hboot_ONLY_2.11.605.19.zip
    md5: d26b3253358407d459c654e6729a39ca

    rename PG05IMG_no_hboot_2.11.605.19.zip to "PG05IMG",move to your sd card,and flash in hboot.

    this is important! you must flash the PG05IMG_no_hboot_2.11.605.19.zip first

    after successfully flashing that,you will be on unrooted gingerbread with an eng s-off bootloader. delete the PG05IMG file from your sd card. now place the PG05IMG_hboot_ONLY_2.11.605.19.zip on your sd card. check the md5. once youve verified it matches,you can rename PG05IMG and flash it.

    again, only flash the hboot file after you have successfully flashed the rom.

    now you are 100% stock on latest firmware. unrooted gingerbread 2.11.605.19 with *locked* 1.05.0000 s-on bootloader.

    as always,be as cautious as possible doing hboot flashes,and follow directions in the http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html to flash these files if youre unfamiliar with hboot flashing.

    *please start a new thread before attempting this if any part of this confuses you. without a bootloader your phone is a paperweight,so we want to help you prior to making any mistakes ;)
    __________________________________________________________________________________


    some other info
    *make sure you read this:
    [WARNING] Do not downgrade to 1.0xxxxx after root

    *some advice for linux/ubuntu users on unrooting can be found in this thread,in post #233,special thanks to user lovebuntu :cool:

    *last and not least the standard discalaimer. i take no credit for anything listed in this post,i am only responsible for placing the information here in one spot. please do your research before attempting to modify your phone,i take no responsibility if any of the methods listed above aid you in turning yout thunderbolt into an expensive paperweight.

    heres a link to the old manual rooting methods thread,for anyone interested: http://androidforums.com/thunderbol...ting-methods-archived-outdated-8-14-11-a.html

    Advertisement
    :
  2. WormDoes

    WormDoes Well-Known Member

    claiming this post for "unroot with no usb" directions. i hope worm doesnt mind ;)

    this post is for unrooting without a working usb port. it assumes you are on some sort of rooted rom,so if youve allready run an RUU,youll need to re-root it before using this to remove revolutionarys or shadowmites permanent patched hboot.

    1)install this wifi over adb app on your phone: https://market.android.com/details?...251bGwsMSwyLDEsImNvbS50dHhhcHBzLndpZmlhZGIiXQ.. im sure others will work,but i used this one and it worked great.

    2)download miniadb_tbolt2.zip from here: mini-adb_tbolt2.zip
    md5: ef01f616471673d3eeb71b4cac4b8118

    3)set up adb:
    -extract miniadb_tbolt2.zip and place the unzipped folder onto the root of your C\ drive on your PC
    -open a command window. windows 7,click on start bubble,type "command" in the search box. a small black window should open up

    4)prepair your phone
    -go to settings/display and set your time out to NEVER sleep. *this is important.
    -launch the app
    -touch the "turn on" button

    5)connect and write new hboot
    -change to your miniadb_tbolt2 directory by typing this command in your command window: cd c:\miniadb_tbolt2 this should change your command prompt to: "c:\miniadb_tbolt2>"
    -enter the command on the screen of your phone to connect to adb over wireless. in my case it was : adb connect 192.168.1.68:5555 i have no idea if it will be different in other cases

    enter the following commands,one at a time. all commands will be bold from this point forward. additional comments will be blue or red

    adb devices should return the number you typed in above. in my case it was 192.168.1.68:5555

    adb push busybox /data/local/

    adb push hbooteng.nb0 /data/local/

    adb shell watch your phone. you may have to allow superuser permissions. you may have to type SU to change your prompt from a $ to a # **you will need the # promt to continue**

    chmod 777 /data/local/busybox

    /data/local/busybox md5sum /data/local/hbooteng.nb0 checking the old eng hboot. this must output 6991368ee2deaf182048a3ed9d3c0fcb if it does not,STOP redownload,and start over.do not procede if it doesnt match

    dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18 write the new hboot.

    /data/local/busybox md5sum /dev/block/mmcblk0p18 confirm proper write. again: the ouput MUST be 6991368ee2deaf182048a3ed9d3c0fcb if it is not, STOP! do NOT reboot! doing so could brick your phone. seek help. try and repeat the 2 steps prior to this one.

    assuming your md5 matched,reboot. you can reboot manually on your phone,or:

    exit back ty your mini-adb_tbolt2> prompt

    adb reboot this will break your wifi connectivity,but thats ok,your done.

    after your phone reboots,you should be running the original,overwritable, eng 1.04.2000 hboot. verify by booting to hboot.

    6)you can now follow the original directions in the first post: Putting current stock firmware and s-on back onto the phone you will need a card reader to transfer the PG05IMG to your sd card.

    i have tested this and it worked for me,but i am radio s-off. if someone tests it,please provide feedback as to wether it worked or not :)

    here is what your adb session should look like:

    Code (Text):
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Scott>[COLOR="Red"]cd c:\tbolt[/COLOR]

    c:\tbolt>[COLOR="red"]adb connect 192.168.1.68:5555[/COLOR]
    connected to 192.168.1.68:5555

    c:\tbolt>[COLOR="red"]adb devices[/COLOR]
    List of devices attached
    192.168.1.68:5555       device


    c:\tbolt>[COLOR="red"]adb push busybox /data/local/[/COLOR]
    641 KB/s (1062992 bytes in 1.618s)

    c:\tbolt>[COLOR="red"]adb push hbooteng.nb0 /data/local/[/COLOR]
    620 KB/s (1048576 bytes in 1.649s)

    c:\tbolt>[COLOR="red"]adb shell[/COLOR]
    $ [COLOR="red"]su[/COLOR]
    su
    # [COLOR="red"]chmod 777 /data/local/busybox[/COLOR]
    chmod 777 /data/local/busybox
    #[COLOR="red"] /data/local/busybox md5sum /data/local/hbooteng.nb0[/COLOR]
    /data/local/busybox md5sum /data/local/hbooteng.nb0
    6991368ee2deaf182048a3ed9d3c0fcb  /data/local/hbooteng.nb0
    # [COLOR="red"]dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18[/COLOR]
    dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    2048+0 records in
    2048+0 records out
    1048576 bytes transferred in 0.415 secs (2526689 bytes/sec)
    # [COLOR="red"]/data/local/busybox md5sum /dev/block/mmcblk0p18[/COLOR]
    /data/local/busybox md5sum /dev/block/mmcblk0p18
    6991368ee2deaf182048a3ed9d3c0fcb  /dev/block/mmcblk0p18
    #[COLOR="Red"] exit[/COLOR]
    exit
    $ [COLOR="red"]exit[/COLOR]
    exit

    c:\tbolt>[COLOR="red"]adb reboot[/COLOR]
    Teener21 likes this.
  3. scotty85

    scotty85 Guides Guide

    rooted stock roms(flash in recovery.does not overwrite radios,recovery,or hboot. these are just like other roms you flash,but are pre-rooted stock firmware):

    US/Verizon
    -MR1(1.13.605.7)
    [ROM] Plain Jane 1.13.605.7 (aka MR1, OTA, v2) 5-15-2011 - xda-developers

    -MR2(1.70.605.0)
    [ROM] Official 1.70.605.0 MR2 OTA Deodexed Rooted Busybox Mirrors Added :D - xda-developers

    -GingerBread OTA(2.11.605.5)
    [Rom][Rooted] 2.11.605.5 Full Stock

    -minor GB OTA(2.11.605.9)
    http://www.htcthunderbolt4g.com/htc...breadrockv1-0-v1-1-(newest-gingerbread-leak)/

    -minor GB OTA(2.11.605.19)
    http://androidforums.com/thunderbol...ted-4-18-12-rooted-ota-2-11-605-19-files.html

    Puerto Rico/Open Mobile
    -1.01.1520.0 leak
    [ROM][GB][UPDATED] Thunderbolt RUU MR4 [1/24/2012][MMS FIX] - RootzWiki

    RUUs(these will return your radio,recovery,etc. to 100% factory. if rooted via revolutionary,permanent s-off will remain. if rooted "old skool" the 1.04.2000 eng hboot will be overwritten)
    *warning* flashing certain RUUs overtop of the 1.04.2000 eng hboot will cause a security warning.
    if you need to return to stock,ask for help,or go to the http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html for themost current directions.


    US/Verizon
    PG05IMG files(rename PG05IMG and flash in hboot)
    -shipping firmweare(1.12.605.6)
    [ROM]Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_N V_8k_1.41_9k_1.64_release - xda-developers

    -minor update(1.12.605.9)
    [PG05IMG]Mecha_VERIZON_WWE_1.12.605.9_Radio_1.16.00.0223r_N V_8k_1.41_9k_1.64_release - xda-developers

    -MR1(1.13.605.7)
    [ruu + update.zip][MR1 aka First OTA] May 12th OTA - 1.13.605.7 - xda-developers

    -MR2(1.70.605.0)
    [RUU LEAK] Froyo 1.70.605.0 Radio 1.39.00.0627r - xda-developers

    -GingerBread OTA(2.11.605.5)
    2011/10/24/exclusive-gingerbread-build-2-11-605-5-for-the-htc-thunderbolt-fixes-several-issues-from-the-previous-leak/
    mirror: http://www.wupload.com/file/2661892397/AndroidPolice_PG05IMG_Mecha_2.11.605.5.zip

    -minor GB OTA(2.11.605.9)
    Multiupload.com - upload your files to multiple file hosting sites!

    -minor GB OTA(2.11.605.19)
    http://www.androidpolice.com/2012/0...t-no-its-not-ics-but-it-does-fix-some-things/


    .exe files(these are firmware run on your pc with phone pluged in. download,open,and follow the onscreen prompts)
    -MR1(1.13.605.7)
    [ROM]RUU_Mecha_VERIZON_WWE_1.13.605.7_Radio_1.16.00.040 2w_1_NV_8k_1.41_9k_1.64 - xda-developers

    -MR2(1.70.605.0)
    [ROM]RUU_Mecha_S_VERIZON_WWE_1.70.605.0_Radio_0.01.69.0 625r_NV_8K_1.41_9K_1.64 - xda-developers

    -official gingerbread OTA(2.11.605.5) RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.5_Radio_0.01.78.0906w_2__NV_8K_1.41_9K_1.64_release_219938_signed.exe - download now for free. File sharing. Software file sharing. Free file hosting. File upload. FileFactory.com

    -minor GB OTA(2.11.605.9)
    RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed.exe - download now for free. File sharing. Software file sharing. Free file hosting. File upload. FileFactory.com

    Puerto Rico/Open Mobile

    PG05IMG files(rename PG05IMG and flash in hboot)
    *note: these will most likely need to be placed on a "gold card" to flash on a vzw branded phone

    .exe files(these are firmware run on your pc with phone pluged in. download,open,and follow the onscreen prompts)
    *note:prolly not flashable a vzw branded phone
    1.01.1520.0 leak
    FileFactory Premium

    last and not least:
    collection of shipped roms for thunderbolt(mecha)
    Whatstreet likes this.
  4. scotty85

    scotty85 Guides Guide

    recently there was a need to unroot without a functional screen. i am including this here,as it will work if you have non functioning power or volume keys :) the only prerequesite is that you be able to get into "fastboot" somehow. this can be done several ways:
    1)entering the adb command "adb reboot bootloader" as described in the directions below.
    2)thru an app like quickboot
    3) thru hboot in this manner:
    -power off
    -hold volume down
    -hold power while continuing to hold volume down untill you get to hboot. press power to enter fastboot.
    *note that #3 will not work if you have "fastboot" checked in settings/power.

    *if you wish to make a backup with amon-ra recovery prior to/in conjunction with this procedure,see the directions here in post #217

    so if you cant see anything on your screen,or have non-working buttons heres what you need to do to unroot:

    download these 2 .zip files(from the original root/unroot thread):

    1)PG05IMG_no_hboot_2.11.605.9.zip
    md5: 3e189b6c85ea7da1e26e12a5cd7b1ab0

    2)PG05IMG_hboot_ONLY_2.11.605.9.zip
    md5: d26b3253358407d459c654e6729a39ca

    then follow these directions(also from the original root/unroot thread):
    Setting up adb and removing the permanent hboot if youve never used adb before
    1)if you no longer have the htc drivers that you installed when rooting with revolutionary,download them again from here on revolutionarys website.
    2)next download this file (mirror)to somewhere convenient that youll be able to find it,like your desktop,or a "downloads" folder. it contains some adb tools.
    3)the following directions were using windows 7 and chrome browser. other OS may be slightly different-the end result is you want unzipped,inside tbolt folder to be on the root of your C: drive.
    -find the tbolt.zipdownload
    -click on tbolt.zip download and open it.
    -inside tbolt.zip,there is a folder labled tbolt. drag it to the root of C:. inside tbolt is the unpermanent hboot and some adb tools.

    3a) once you have the "tbolt" folder on the root of your c/ drive,drag the entire PG05IMG_no_hboot_2.11.605.9.zip into it the tbolt folder,along with the tools and files that are allready there. dont unzip it.

    3b) open the PG05IMG_hboot_ONLY_2.11.605.9 .zip file. if you have to,use 7 zip or the equivalent to extract it. inside there is an image: "hboot_7630_1.05.0000_110719.nb0" youll want to drag and drop it,or copy and paste it, into the tbolt folder,along with PG05blah blah,and all the tools.

    4) charge your Thunderbolt to 100%
    5)click on then "start" bubble in the lower left corner of your screen. type "command" in the search window and hit enter. this will open a small black command window. plug in your thunderbolt.
    6)enter the following command(by typing or copy/paste):
    Code (Text):
    cd c:\tbolt
    you should see your promt in the window change to: c:\tbolt>
    7)enter the follwing command:

    Code (Text):
    adb devices
    assuming your custom rom has usb debugging disabled by default,or you are able to enable usb debugging on a stock rom, then you should see your serial number.

    enter the commands,1 at a time:
    8)
    Code (Text):
    md5sums PG05IMG_no_hboot_2.11.605.9.zip
    it may take a minute,but it should output 3e189b6c85ea7da1e26e12a5cd7b1ab0

    9)
    Code (Text):
    md5sums hboot_7630_1.05.0000_110719.nb0
    output should be e1e330356ec5c889a92be1b5ef6c853d

    10)
    Code (Text):
    adb reboot bootloader
    11)
    Code (Text):
    fastboot devices
    should output serial number

    11a)
    Code (Text):
    fastboot erase cache
    12)
    Code (Text):
    fastboot oem rebootRUU
    13)
    Code (Text):
    fastboot devices
    should output serial number. if not,youll have get to pull the battery and get back into fastboot somehow. if you have a no screen,but working buttons,power on into hboot via power/vol down. wait a couple minutes. press power to select fastboot. i know this will be nerveracking cause you cant see the screen :eek: if you have a screen and no buttons,you will have to let thephone boot,then use #1 or #2 above. do fastboot devices again. then go back to the 12) fastboot oem rebootRUU step,and continue. you need to get your serial number at step 13 before you can continue. otherwise youll just get a "<waiting for device>" error.

    14)once youve gotten your serial number at step 13,flash the pg05 no hboot file with this command:
    Code (Text):
    fastboot flash zip PG05IMG_no_hboot_2.11.605.9.zip
    remember,for it to work,its important that PG05IMG_no_hboot_2.11.605.9.zip be in the tbolt folder along with adb,fastboot,etc.

    it will do a bunch of stuff. when its done,youll see:
    "OKAY [213.940s]
    finished. total time: 287.032s"

    15)then:
    Code (Text):
    fastboot devices
    assuming you see a serial number,then:

    16)then:
    Code (Text):
    fastboot reboot-bootloader
    17)unlock revolutionary hboot:
    Code (Text):
    fastboot oem mw 8d08ac54 1 31302E30
    18)write 1.05.0000 hboot(md5 above matched,right? ;))
    Code (Text):
    fastboot flash hboot hboot_7630_1.05.0000_110719.nb0
    19)then:
    Code (Text):
    fastboot reboot-bootloader
    20)then:
    Code (Text):
    fastboot reboot
    your phone should now be completely stock. if you can see it :)

    and heres what you should see on the PC(red are my inputs):
    Code (Text):
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Scott>[COLOR="Red"]cd c:\tbolt[/COLOR]

    c:\tbolt>[COLOR="Red"]adb devices[/COLOR]
    adb server is out of date.  killing...
    * daemon started successfully *
    List of devices attached
    HT12CS012936    device


    c:\tbolt>[COLOR="red"]md5sums PG05IMG_no_hboot_2.11.605.9.zip[/COLOR]

    MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
    Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
    Type md5sums -h for help

    [Path] / filename                              MD5 sum
    -------------------------------------------------------------------------------
    [c:\tbolt\]
    PG05IMG_no_hboot_2.11.605.9.zip           100% 3e189b6c85ea7da1e26e12a5cd7b1ab0

    c:\tbolt>[COLOR="red"]md5sums hboot_7630_1.05.0000_110719.nb0[/COLOR]

    MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
    Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
    Type md5sums -h for help

    [Path] / filename                              MD5 sum
    -------------------------------------------------------------------------------
    [c:\tbolt\]
    hboot_7630_1.05.0000_110719.nb0                e1e330356ec5c889a92be1b5ef6c853d

    c:\tbolt>[COLOR="red"]adb reboot bootloader[/COLOR]

    c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
    HT12CS012936    fastboot

    c:\tbolt>[COLOR="Red"]fastboot erase cache[/COLOR]
                   erasing 'cache'... OKAY [  0.183s]
    finished. total time: 0.184s

    c:\tbolt>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                                  ... OKAY [  0.220s]
    finished. total time: 0.221s

    c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
    HT12CS012936    fastboot

    c:\tbolt>[COLOR="red"]fastboot flash zip PG05IMG_no_hboot_2.11.605.9.zip[/COLOR]
         sending 'zip' (451423 KB)... OKAY [ 72.398s]
                     writing 'zip'... INFOzip header checking...
    INFOzip info parsing...
    INFOchecking model ID...
    INFOchecking custom ID...
    INFOstart image[tp] unzipping & flushing...
    INFO[RUU]UZ,tp,0
    INFO[RUU]UZ,tp,100
    INFO[RUU]WP,tp,0
    INFOstart image[boot] unzipping & flushing...
    INFO[RUU]UZ,boot,0
    INFO[RUU]UZ,boot,32
    INFO[RUU]UZ,boot,76
    INFO[RUU]UZ,boot,100
    INFO[RUU]WP,boot,0
    INFO[RUU]WP,boot,99
    INFO[RUU]WP,boot,100
    INFOstart image[dzdata] unzipping & flushing...
    INFO[RUU]UZ,dzdata,0
    INFO[RUU]UZ,dzdata,99
    INFO[RUU]UZ,dzdata,100
    INFO[RUU]WP,dzdata,0
    INFO[RUU]WP,dzdata,85
    INFO[RUU]WP,dzdata,100
    INFOstart image[mdm9k] unzipping & flushing...
    INFO[RUU]UZ,mdm9k,0
    INFO[RUU]UZ,mdm9k,6
    INFO[RUU]UZ,mdm9k,12
    INFO[RUU]UZ,mdm9k,18
    INFO[RUU]UZ,mdm9k,24
    INFO[RUU]UZ,mdm9k,30
    INFO[RUU]UZ,mdm9k,36
    INFO[RUU]UZ,mdm9k,43
    INFO[RUU]UZ,mdm9k,49
    INFO[RUU]UZ,mdm9k,55
    INFO[RUU]UZ,mdm9k,61
    INFO[RUU]UZ,mdm9k,67
    INFO[RUU]UZ,mdm9k,74
    INFO[RUU]UZ,mdm9k,80
    INFO[RUU]UZ,mdm9k,86
    INFO[RUU]UZ,mdm9k,92
    INFO[RUU]UZ,mdm9k,98
    INFO[RUU]UZ,mdm9k,100
    INFO[RUU]WP,mdm9k,0
    INFO[RUU]WP,mdm9k,6
    INFO[RUU]WP,mdm9k,12
    INFO[RUU]WP,mdm9k,18
    INFO[RUU]WP,mdm9k,24
    INFO[RUU]WP,mdm9k,30
    INFO[RUU]WP,mdm9k,36
    INFO[RUU]WP,mdm9k,42
    INFO[RUU]WP,mdm9k,48
    INFO[RUU]WP,mdm9k,54
    INFO[RUU]WP,mdm9k,60
    INFO[RUU]WP,mdm9k,69
    INFO[RUU]WP,mdm9k,75
    INFO[RUU]WP,mdm9k,81
    INFO[RUU]WP,mdm9k,87
    INFO[RUU]WP,mdm9k,100
    INFOstart image[recovery] unzipping & flushing...
    INFO[RUU]UZ,recovery,0
    INFO[RUU]UZ,recovery,21
    INFO[RUU]UZ,recovery,42
    INFO[RUU]UZ,recovery,64
    INFO[RUU]UZ,recovery,85
    INFO[RUU]UZ,recovery,100
    INFO[RUU]WP,recovery,0
    INFO[RUU]WP,recovery,99
    INFO[RUU]WP,recovery,100
    INFOstart image[sp1] unzipping & flushing...
    INFO[RUU]UZ,sp1,0
    INFO[RUU]UZ,sp1,100
    INFO[RUU]WP,sp1,0
    INFO[RUU]WP,sp1,100
    INFOstart image[system] unzipping & flushing...
    INFO[RUU]UZ,system,0
    INFO[RUU]UZ,system,1
    INFO[RUU]UZ,system,3
    INFO[RUU]UZ,system,5
    INFO[RUU]UZ,system,7
    INFO[RUU]UZ,system,9
    INFO[RUU]UZ,system,11
    INFO[RUU]UZ,system,12
    INFO[RUU]UZ,system,14
    INFO[RUU]UZ,system,16
    INFO[RUU]UZ,system,18
    INFO[RUU]UZ,system,20
    INFO[RUU]UZ,system,22
    INFO[RUU]UZ,system,24
    INFO[RUU]WP,system,0
    INFO[RUU]WP,system,1
    INFO[RUU]WP,system,3
    INFO[RUU]WP,system,5
    INFO[RUU]WP,system,7
    INFO[RUU]WP,system,9
    INFO[RUU]WP,system,11
    INFO[RUU]WP,system,12
    INFO[RUU]WP,system,14
    INFO[RUU]WP,system,16
    INFO[RUU]WP,system,18
    INFO[RUU]WP,system,20
    INFO[RUU]WP,system,22
    INFO[RUU]WP,system,24
    INFO[RUU]UZ,system,24
    INFO[RUU]UZ,system,25
    INFO[RUU]UZ,system,27
    INFO[RUU]UZ,system,29
    INFO[RUU]UZ,system,31
    INFO[RUU]UZ,system,33
    INFO[RUU]UZ,system,35
    INFO[RUU]UZ,system,36
    INFO[RUU]UZ,system,38
    INFO[RUU]UZ,system,40
    INFO[RUU]UZ,system,42
    INFO[RUU]UZ,system,43
    INFO[RUU]UZ,system,45
    INFO[RUU]UZ,system,47
    INFO[RUU]UZ,system,48
    INFO[RUU]WP,system,24
    INFO[RUU]WP,system,25
    INFO[RUU]WP,system,27
    INFO[RUU]WP,system,29
    INFO[RUU]WP,system,31
    INFO[RUU]WP,system,33
    INFO[RUU]WP,system,35
    INFO[RUU]WP,system,36
    INFO[RUU]WP,system,38
    INFO[RUU]WP,system,40
    INFO[RUU]WP,system,42
    INFO[RUU]WP,system,44
    INFO[RUU]WP,system,46
    INFO[RUU]WP,system,48
    INFO[RUU]UZ,system,48
    INFO[RUU]UZ,system,50
    INFO[RUU]UZ,system,51
    INFO[RUU]UZ,system,53
    INFO[RUU]UZ,system,55
    INFO[RUU]UZ,system,57
    INFO[RUU]UZ,system,58
    INFO[RUU]UZ,system,60
    INFO[RUU]UZ,system,61
    INFO[RUU]UZ,system,63
    INFO[RUU]UZ,system,64
    INFO[RUU]UZ,system,66
    INFO[RUU]UZ,system,68
    INFO[RUU]UZ,system,70
    INFO[RUU]UZ,system,71
    INFO[RUU]UZ,system,72
    INFO[RUU]WP,system,48
    INFO[RUU]WP,system,49
    INFO[RUU]WP,system,51
    INFO[RUU]WP,system,53
    INFO[RUU]WP,system,55
    INFO[RUU]WP,system,57
    INFO[RUU]WP,system,59
    INFO[RUU]WP,system,60
    INFO[RUU]WP,system,62
    INFO[RUU]WP,system,64
    INFO[RUU]WP,system,66
    INFO[RUU]WP,system,68
    INFO[RUU]WP,system,70
    INFO[RUU]WP,system,72
    INFO[RUU]UZ,system,72
    INFO[RUU]UZ,system,73
    INFO[RUU]UZ,system,74
    INFO[RUU]UZ,system,76
    INFO[RUU]UZ,system,78
    INFO[RUU]UZ,system,79
    INFO[RUU]UZ,system,81
    INFO[RUU]UZ,system,83
    INFO[RUU]UZ,system,84
    INFO[RUU]UZ,system,85
    INFO[RUU]UZ,system,87
    INFO[RUU]UZ,system,89
    INFO[RUU]UZ,system,91
    INFO[RUU]UZ,system,93
    INFO[RUU]UZ,system,95
    INFO[RUU]UZ,system,96
    INFO[RUU]WP,system,72
    INFO[RUU]WP,system,73
    INFO[RUU]WP,system,75
    INFO[RUU]WP,system,77
    INFO[RUU]WP,system,79
    INFO[RUU]WP,system,81
    INFO[RUU]WP,system,83
    INFO[RUU]WP,system,84
    INFO[RUU]WP,system,86
    INFO[RUU]WP,system,88
    INFO[RUU]WP,system,90
    INFO[RUU]WP,system,92
    INFO[RUU]WP,system,94
    INFO[RUU]WP,system,96
    INFO[RUU]UZ,system,96
    INFO[RUU]UZ,system,96
    INFO[RUU]UZ,system,96
    INFO[RUU]UZ,system,97
    INFO[RUU]UZ,system,97
    INFO[RUU]UZ,system,98
    INFO[RUU]UZ,system,98
    INFO[RUU]UZ,system,99
    INFO[RUU]UZ,system,99
    INFO[RUU]UZ,system,100
    INFO[RUU]WP,system,96
    INFO[RUU]WP,system,98
    INFO[RUU]WP,system,100
    INFOstart image[tp] unzipping & flushing...
    INFO[RUU]UZ,tp,0
    INFO[RUU]UZ,tp,100
    INFOstart image[radio] unzipping & flushing...
    INFO[RUU]UZ,radio,0
    INFO[RUU]UZ,radio,7
    INFO[RUU]UZ,radio,12
    INFO[RUU]UZ,radio,18
    INFO[RUU]UZ,radio,26
    INFO[RUU]UZ,radio,33
    INFO[RUU]UZ,radio,41
    INFO[RUU]UZ,radio,48
    INFO[RUU]UZ,radio,56
    INFO[RUU]UZ,radio,63
    INFO[RUU]UZ,radio,71
    INFO[RUU]UZ,radio,78
    INFO[RUU]UZ,radio,86
    INFO[RUU]UZ,radio,93
    INFO[RUU]UZ,radio,100
    INFO[RUU]WP,radio,0
    INFO[RUU]WP,radio,5
    INFO[RUU]WP,radio,13
    INFO[RUU]WP,radio,21
    INFO[RUU]WP,radio,28
    INFO[RUU]WP,radio,36
    INFO[RUU]WP,radio,46
    INFO[RUU]WP,radio,100
    OKAY [208.075s]
    finished. total time: 280.474s

    c:\tbolt>[COLOR="red"]fastboot devices[/COLOR]
    HT12CS012936    fastboot

    c:\tbolt>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
         rebooting into bootloader... OKAY [  0.157s]
    finished. total time: 0.158s

    c:\tbolt>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
                                  ... OKAY [  0.006s]
    finished. total time: 0.006s

    c:\tbolt>[COLOR="red"]fastboot flash hboot hboot_7630_1.05.0000_110719.nb0[/COLOR]
         sending 'hboot' (1024 KB)... OKAY [  0.185s]
                   writing 'hboot'... OKAY [  0.226s]
    finished. total time: 0.413s

    c:\tbolt>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
         rebooting into bootloader... OKAY [  0.230s]
    finished. total time: 0.231s

    c:\tbolt>[COLOR="red"]fastboot reboot[/COLOR]
                         rebooting...
    finished. total time: 0.144s

    c:\tbolt>
    if yo have a black screen and want a little peace of mind that the above worked and got you back to stock,you can enter fastboot getvar all with the phone in fastboot(right after step 19 in the procedure would be a good time to do it). this will list a bunch of variables that you can double check. this is completely optional and for peace of mind only. nothing wrong with not doing it. heres basically what you will see:
    Code (Text):

    c:\tbolt>[COLOR="Red"]fastboot getvar all[/COLOR]
    INFOversion: 0.5
    INFOversion-bootloader: 1.04.2000 [COLOR="Blue"]<-this should say [B]1.05.0000[/B][/COLOR]
    INFOversion-baseband: 1.48.00.0101w [COLOR="Blue"]<-this should be [B]1.48.00.0930w[/B] [/COLOR]
    INFOversion-cpld: None
    INFOversion-microp: /
    INFOversion-main: 2.10.605.1 [COLOR="blue"]<-this should be [B]2.11.605.9[/B][/COLOR]
    INFOserialno: HTxxxxxxxx
    INFOimei: 355195000000017
    INFOproduct: mecha
    INFOplatform: HBOOT-7630
    INFOmodelid: PG05*****
    INFOcidnum: 11111111 [COLOR="blue"]<- this should be [B]VZW_001[/B][/COLOR]
    INFObattery-status: good
    INFObattery-voltage: 4112mV
    INFOpartition-layout: Generic
    INFOsecurity: off [COLOR="Blue"]<-this should say [B]on[/B][/COLOR]
    INFObuild-mode: ENG [COLOR="blue"]<-this should be [B]SHIP[/B][/COLOR]
    INFOboot-mode: FASTBOOT
    INFOcommitno-bootloader: 9a13ccd2
    INFOhbootpreupdate: 12
    INFOgencheckpt: 0
    INFOregion-id: not support
    all: Done!
    finished. total time: 0.023s
     
    *note that this is my rooted phone,but it gives you the idea :)
    loveubuntu and Yeahha like this.
  5. parrc

    parrc Member

    I dont have the pink revolutionary at the top of my page???? It also says S-on
    Can you help i tried re installing and that didn't work.
    thanks chris.
  6. scotty85

    scotty85 Guides Guide

    the unroot method may change in the future,but for now i will leave it as is.

    if you are running a permant patch hboot(revolutionary or shadowmite) and find yourself without a working touchscreen or usb port,fear not, you can still get back to full stock s-on.

    download these files:

    -the current "no_hboot" file from the OP.
    -the current "hboot_only" file from the OP
    -the downgrader hboot from here: www.mediafire.com/?koldajo4245f6v2

    inside the zip,there is an md5 for the zip inside. make sure that you check it

    once youve verified the integrity of the zip inside the download,the directions are simple:

    1)rename the downgrader zip from inside the download to PG05IMG and flash in hboot. reboot
    2)rename PG05IMG,and flash the "no_hboot" file. reboot
    3)rename PG05IMG and flash the "hboot_only" file. you MUST FLASH IT LAST
    *this is important*
  7. parrc

    parrc Member

    I fixed it. I removed all of the downloads and re-placed with new ones. Not sure what happened but im Rooted TB user now.
    Thanks Scotty 85
    I would like to know what are the first things to do now im rooted. I have the wireless tether app. Taking full advantage of that one.
    Give me some other necessities if you have some great ones...
  8. Yeahha

    Yeahha Usually off topic VIP Member

    Titanium backup and root explorer are both good root apps.

    I would suggest you look into flashing a rom to get rid of bloatware as well as getting to try out newer versions of sense or AOSP.
    scotty85 likes this.
  9. scotty85

    scotty85 Guides Guide

    Awesome. Glad you got it working :cool: yeahhas suggestions are good,and you can find alot of info in the "how to" sticky thread at the top of the forum. Post up if you have any questions :)

    Last and not least,your cigar and blazer are on the table :D
  10. fixxxer1022

    fixxxer1022 Well-Known Member

    after i remove the s-off 'revolutionary" hboot can i flash the stock official GB update? because it gives you a new hboot correct?

    i need to ship my phone back to verizon and i told them i got the ota update.
  11. Yeahha

    Yeahha Usually off topic VIP Member

    Yeah you should use the RUU once you get revolutionary hboot off of it and it will put the stock hboot on there.

    So you got the charge?
  12. scotty85

    scotty85 Guides Guide

    I would be extremely careful doing this. After flashing the old Eng 1.04.2000 hboot, the safest way to flash new firmware and hboot is to remove the hboot from the ruu,flash the ruu, then flash only the hboot second.

    There is a 1.05.0000 hboot in he hboots,radios,and recoveries thread. Since I haven't uploaded a gingerbread "no hboot" ruu,the best thing to is this:

    1)flash gb ruu with revolutionary hboot in place. This will safely get the ruu onto the phone first,since the revolutionary hboot will block the 1.05.0000 install.
    2)follow the guide to unlock the permanent revolutionary hboot and install the old Eng 1.04.2000 hboot.
    3)flash the 1.05.0000 hboot from the radios,recoveries,hboots thread linked above.

    attempting to falsh the GB RUU in its entirety overtop of custom firmware may or may not result in a security warning. if that happens,youre stuck with the phone until a newer ruu comes out :eek: i personally would not risk it.

    youd have been better off telling them that the phone still had mr2,IMO. then you could have used the unroot files above.
    fixxxer1022 likes this.
  13. fixxxer1022

    fixxxer1022 Well-Known Member

    Ill just put mr2 on it they wont care. As long as its not rooted im good.
  14. fixxxer1022

    fixxxer1022 Well-Known Member

    Yeah they are shipping me a charge. Im done with htc. The new security issue bugs me.
  15. Yeahha

    Yeahha Usually off topic VIP Member

    I hear you. I only run AOSP so I am unaffected by the security bug but depending on how HTC handles this I could see it being a dealbreaker for people come time for their upgrade. Did you get MR2 running?
  16. fixxxer1022

    fixxxer1022 Well-Known Member

    Im on cm7 but its just the principle of the issue at hand. I talked to htc and they refuse to convey how they will rectify this. The charge will tide me over until the prime hits. I was going to get the vigor but forget it now.

    No im waiting to s-on unroot until my charge gets here in yhe next few days. Im debating putting ginger ota on it or just stick to mr2 before i ship back. Not sure whats best as i told verizon i got the gingerbread update.
  17. Yeahha

    Yeahha Usually off topic VIP Member

    If you get MR2 stock on it with the stock bootloader then using the ruu to GB shouldn't be an issue. I think the security warning scotty said something about would be trying to use the RUU a s-on bootloader and a custom rom
  18. scotty85

    scotty85 Guides Guide

    IMO this is a little childish. i do not believe htc has put files on intentionally to be exploited and our data manipulated. while this is a serious issue, what makes you think there are no such files in the charge firmware? just because no ones found them yet,doesnt mean they arent there. i like htc hardware. how they handle this situation will either passify me,or make me extremely disapointed. but that wont change the fact that i like the hardware. im just going to root whatever device i get anyway,it doesnt matter really,what files mfgrs sneek into their stock roms as ill never use them.

    that is correct,sir,once the phone is mr2 s-on stock,flashing the GB ruu is perfectly safe,it just involes alot more hboot flashing than what i recceomended above. just double and triple check md5s and it should be fine.

    the prollem is thw way the hboot checks the firmware before flashing the rest of the RUU. if your on cm7,and flash certain RUUs(mr1 for example,not 100%sure on mr2 or GB),the hboot flashes first,logically,as it flashes the rest of the firmware. after the hboot flashes it looks at cm7 and may say "WTF!" and throw up the security warning. or it may not. we dont know until someone tries it and reports.

    thats why the 100% safest way to flash an RUU whose outcome you dont know is to always flash the ruu first,hboot second.
  19. fixxxer1022

    fixxxer1022 Well-Known Member

    So i downgrade to mr2 then flash the stock s-on hboot then i can flash the GB ota without removing the new hboot from the zip? Did i understand this correctly?


    Also scotty alot of people got replacement phones today over this. Its not childish in any way.
  20. scotty85

    scotty85 Guides Guide

    yes. follow the guide above. flash no hboot first,hboot only second. then you can flash the entire 2.11.605.3 ruu if you wish.


    doesnt mean alot of people arent childish. if alot of people jumped off a bridge,would you do it?

    i agree its a big deal. but we dont even know how they will handle it,why they did it inthe first place. the hardware is the same now as it was before and you and most of these other folks were happy with it. you were running cm7 and not even in any danger as those files arent there.

    "lots of people" are using it as an excuse to get new phones.

    just my opinion.
    fixxxer1022 likes this.
  21. Yeahha

    Yeahha Usually off topic VIP Member

    Yeah if you get stock MR2 on there you can RUU the GB OTA without any worries, given you have the s-on hboot and everything else stock.


    I saw the posts at rootz about it, I don't run sense so it won't affect me but I can see why people wouldn't want to have to worry about it and HTC hasn't really address it at all I really expected more out of them.
  22. fixxxer1022

    fixxxer1022 Well-Known Member

    Ill unroot tomorrow night and report back, thanks guys. Now to do some research on rooting my charge. Seems a bit more difficult.
  23. fixxxer1022

    fixxxer1022 Well-Known Member

    Yeah htc needs to rectify this and soon.
  24. Yeahha

    Yeahha Usually off topic VIP Member

    Good luck man, it shouldn't be that difficult to root the charge, just not a solution like revolutionary but if you rooted with the old manual process then it shouldn't be any issue. Let us know how it goes.
Loading...

Share This Page