• XDA Forums have been migrated to XenForo. To discuss, report bugs and other issues, use this thread.

current thunderbolt root thread

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,054
0
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.

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
Revolutionary by unrevoked/alpharev 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. (need verification downgrading still works)
*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 :)
__________________________________________________________________________________
how to 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

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:
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]
__________________________________________________________________________________
[ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 is outdated,but linked for info and nastalgia :)

also,see my unroot thread here: [HOW TO]return to stock (gingerbread) from revolutionary or normal hboot(11/2/11)
 
Last edited:

KrisPeezy

New member
Feb 14, 2011
283
33
0
So.Cal
hey guys, I was trying to root my friends Tbolt last week and failed... Here's what i've tried:
  • downgraded to RUU before the update(the one ending in 5)
  • installed htc drivers from revolutionary.io
  • ran revolutionary (where it hung at "waiting for device" for the first computer, and then hang at "waiting for fastboot" at the 2nd computer)
  • tried uninstalling pdanet(don't have any of the other apps listed in revolutionary.io that have reported to interfere)
  • tried the fr3vo temp root through mini adb and then running revolutionary(still hung at "waiting for fastboot")
  • uninstalled and reinstalled drivers several times(it looked like it updated drivers when i plugged in the phone, so sometimes i reinstalled while revolutionary was waiting. Also disconnected from the internet to prevent it from downloading any new drivers with windows)
  • reupdated to OTA and tried fr3vo again
  • redowngraded after running into an error in revolutionary because I unplugged at some point
  • I haven't had a chance to try the manual method through adb because I don't really have that much time when I do get a hold of his phone

Any Ideas on what I can do?

btw, when I said it would hang, I waited at least 30 minutes each time, and it would be stuck at the points I listed above.
 

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,054
0
its got to be either a driver issue,or a "something on your pc interfering" issue. other folks ive seen with similar issues have had success by using different PCs.

you could try updating the drivers with the phone in fastboot.

if you open a cmd window,cd to your adb/fastboot directory,adb reboot bootloader,then fastboot devices do you get a serial number?

i assume there is no htc sync installed?

if you absolutely had to,you could temp root with fre3vo,then downgrade to prerease firmware,and root "old skool". afterward id flash shadowmites permanent hboot. or just substitute it for the eng hboot in the process.
 

KrisPeezy

New member
Feb 14, 2011
283
33
0
So.Cal
I guess I've just gotta keep trying on different pc's...

scotty i've tried updating drivers while in fastboot, and i'm pretty sure the device was being seen by adb. It's my friend's phone, so I do have limited access and probly can't run those commands anytime soon

Correct, no htc sync installed.

supra, i thought it was pdanet too, so i went to a pc that never had it and i still got stuck.
 

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,054
0
sorry,wish i had some better advice for you. you could try re-downloading revolutionary,if you havent allready,but it sure sounds like something on the PC or the drivers are messing with it.

it would also be worth trying some different usb cables,if you havent allready.
 
  • Like
Reactions: Ryanmo5

scotty1223

Inactive Recognized Contributor
Jan 3, 2011
2,813
3,054
0
if anyone tries to downgrade from .19 to .5 please let us know if it worked. i dont have access to any s-on phones to test with :)
 

mstinson23

New member
Jul 11, 2011
45
2
0
Tempe AZ
I just wanted to share an issue I just had while trying to root my replacement phone I just got the other day. Everything went fine up until the point where Revoluationary booted my phone down to HBOOT. At that point the process just hung. I had all the proper drivers, etc. It turned out the issue was I was plugged into a USB 3.0 port. The second I moved to a standard USB port the process continued. I have not seen anywhere that you cannot use a USB 3.0 port or that it may cause problems so I thought I would mention this in case anyone else has this issue.

If this is already known and posted somewhere I apologize, but I couldn't find it anywhere. The only reason I got it resolved was by asking on the Revoluationary IRC channel.
 
  • Like
Reactions: scotty1223

lennathi

New member
Mar 31, 2012
35
9
0
Denver, CO
I just wanted to share an issue I just had while trying to root my replacement phone I just got the other day. Everything went fine up until the point where Revoluationary booted my phone down to HBOOT. At that point the process just hung. I had all the proper drivers, etc. It turned out the issue was I was plugged into a USB 3.0 port. The second I moved to a standard USB port the process continued. I have not seen anywhere that you cannot use a USB 3.0 port or that it may cause problems so I thought I would mention this in case anyone else has this issue.

If this is already known and posted somewhere I apologize, but I couldn't find it anywhere. The only reason I got it resolved was by asking on the Revoluationary IRC channel.
I am going to second this.
I have experienced the same problem, but not just with Revolutionary.
ADB seems to not like USB 3 for a few devices.
Specifically my HTC Rezound, my gf's Thunderbolt, and both of our Kindle Fires have issues with USB 3 interaction.
Things hang, fail, or are not detected at all.
This happens on multiple computers each with a different controller chip, one Intel, one Marvell, and another (can't recall atm) .

Sent from my Kindle Fire using xda premium
 
  • Like
Reactions: scotty1223

RunNgun42

New member
Jul 14, 2010
611
83
0
Fantastic tool, made rooting a snap! You should mention that you need to have an SD card installed when you do this, otherwise it skips the superuser install portion of recovery. You can always copy it and reboot into CWM and install manually, but it had me worried there for a minute since I forgot to install an SD card as I was replacing a phone.
 

trter10

New member
Jan 25, 2012
674
464
0
Fantastic tool, made rooting a snap! You should mention that you need to have an SD card installed when you do this, otherwise it skips the superuser install portion of recovery. You can always copy it and reboot into CWM and install manually, but it had me worried there for a minute since I forgot to install an SD card as I was replacing a phone.
Which toll?

Sent from my ADR6400L using Tapatalk 2