Root thunderbolt rooting methods(archived-outdated as of 8/14/11)

[scotty85]

this thread is dedicated to the current known methods of rooting the thunderbolt. if there are new developments,or new methods on other forums,feel free to shoot me a PM or post on the thread,and ill add them to the first post.

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 listfor a list of roms,kernels and mods

for some extra info and "how to"s of rooting see http://androidforums.com/thunderbolt-all-things-root/352729-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.
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 8/14/2011
a new method has just become available that does not wipe your data,or require downloading 2 large RUUs,or require the instalation and use of ADB. all you need are the drivers,and the tool.

see this page for info:
Revolutionary

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

sorry if this page is getting a little confusing. the best method to use IMO is the revolutionary tool,for various reasons. if youre techy,like adb,want to learn adb,or any other reason,feel free to use the manual method,it does still work.

as soon as i get time,i will archive most of the info here,clean everything up and hopefully make it a little clearer. thanks for your support and patience


manual root:(the manual root method is now outdated)
*please note: the manual rooting method become outdated with the most recent OTA to firmware #1.70.605.0. the method still works just fine,but the "upgrade RUU" is 1.13.605.7,and thus,your phone will try and update if you attempt to run this rooted firmware.DO NOT attempt to run the rooted 1.13.605.7 firmware,or attempt to take an OTA update while rooted. see above.

you have 2 options to deal with this:
1)use the guide as is. you will need to flash a rom,and prolly radios IMMEDIATELY after rooting.
2)substitue this upgrade ruu for the one in the guide. some more info about this different upgrade ruu here


[ROOT][ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011

[Prerequisite to Rooting] Android SDK Installer - v3.0 for Windows

Guide to setting up ADB for Ubuntu/Linux

-helpful videos for manual root(watch on you tube to get the links in the video description):

* my advice is to watch all videos to get a general feel for how the manual rooting method works. do not attempt to use any one video as a completel guide. i personally used connection2005s video to set up adb,however your mileage may vary.
*also note that the set up adb videos are not a 2 part thing,they are 2 different videos on how to accomplish the same thing. again,i personally used the first video to get adb set up,but watch them both and then pick wichever youre more comfortable with.

-setting up adb:
from connection2005 on xda:
YouTube - ‪ANDROID SDK Tools (How-To Install)‬‏

*edit:when using this second video, refer to [HOW-TO] ADB for Dummies(How-To Learner's Guide) vanillaTbone has updated the original post with links to his new guide,and allInOne app.
YouTube - ‪How to Root the HTC Thunderbolt, Setting up ADB - Step 1‬‏
-steps 2-9 of the guide:
YouTube - ‪How to Root the HTC Thunderbolt - Version 2.5‬‏

-a copy of my manual root session using windows:

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

C:\Users\Scott>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device


C:\Users\Scott>[COLOR="red"]cd c:\android-sdk-windows\flashables[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb push psneuter /data/local/[/COLOR]
1214 KB/s (585731 bytes in 0.471s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1146 KB/s (1062992 bytes in 0.905s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push misc.img /data/local/[/COLOR]
1462 KB/s (262144 bytes in 0.175s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/psneuter[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/busybox[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]/data/local/psneuter[/COLOR]
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[COLOR="red"] /data/local/busybox md5sum /data/local/misc.img[/COLOR]
/data/local/busybox md5sum /data/local/misc.img
c88dd947eb3b36eec90503a3525ae0de  /data/local/misc.img
#[COLOR="red"] dd if=/data/local/misc.img of=/dev/block/mmcblk0p17[/COLOR]
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
512+0 records in
512+0 records out
262144 bytes transferred in 0.112 secs (2340571 bytes/sec)
# [COLOR="red"]exit[/COLOR]
exit

[COLOR="Blue"]manually move downgrade RUU to SD card[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]

[COLOR="blue"]select bootloader with power button,let hboot flash downgrade RUU,reboot[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device


c:\android-sdk-windows\flashables>[COLOR="red"]adb push psneuter /data/local/[/COLOR]
1440 KB/s (585731 bytes in 0.397s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1693 KB/s (1062992 bytes in 0.613s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb push wpthis /data/local/[/COLOR]
1134 KB/s (679475 bytes in 0.585s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/psneuter[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/busybox[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell chmod 777 /data/local/wpthis[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]/data/local/psneuter[/COLOR]
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[COLOR="red"] /data/local/wpthis[/COLOR]
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000f80 (3968)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-g2447a8d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02d3114, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02d3000
Kernel memory mapped to 0x40001000
Searching for brq filter...
 - Address: 0xc02d3114 + 0x34c
 - 0x2a000012 -> 0xea000012
Done.
# [COLOR="Red"]exit[/COLOR]
exit

c:\android-sdk-windows\flashables>[COLOR="red"]adb push hbooteng.nb0 /data/local/[/COLOR]
1656 KB/s (1048576 bytes in 0.618s)

c:\android-sdk-windows\flashables>[COLOR="red"]adb shell[/COLOR]
#[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.477 secs (2198272 bytes/sec)
#[COLOR="red"] /data/local/busybox md5sum /dev/block/mmcblk0p18[/COLOR]
/data/local/busybox md5sum /dev/block/mmcblk0p18
6991368ee2deaf182048a3ed9d3c0fcb  /dev/block/mmcblk0p18
#

[COLOR="blue"]manually reboot phone.[/COLOR]

[COLOR="blue"]after phone reboots,manually move upgrade RUU to SD card.[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT126S005970    device

c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]

[COLOR="blue"]select bootloader with power button,let hboot flash upgrade RUU,reboot[/COLOR]


c:\android-sdk-windows\flashables>

a couple of people have said they found it helpful,so i thot id go ahead and include it. it may help to see what the output should be to each input. the first time i rooted i sometimes wasnt sure if anything had happend. red=my pasted or typed inputs. blue=additional notes to show what was going on.these are not typed,pasted or outputted.

backing up your data prior to rooting:
added this 7/31/11. just saw it yesterday,it will hopefully become more detailed as time goes on. for now ill leave it here in case advanced useres are interested in the concept or in trying it:
Easy pre-root backup with adb

"easy root" methods:
*please note: the manual method is the only method whose post has been updated to state that it still works with the 1.13.605.7 firmware. i would advise using the manual method over these easy root methods unless you can comfirm with the methods creator that it will still work with the new firmware.
[SCRIPT] Windows One Click Root Method [3/26/11]

[Updated: 3/26]Easyroot + S-Off [Version 1.6.3.11]

[Auto] Root and Unroot (Windows)**Updated**4/20

mac:
[HOWTO] Getting root on your Thunderbolt from start to finish - Mac OS X

easyroot+S-off mac/linux

how to unroot:
by jcase: [HOWTO][HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011

simple unroot: Simple Un-Root!

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

hboot installable firmware

[RUU LEAK] Froyo 1.70.605.0 Radio 1.39.00.0627r official MR2

[RUU] [LEAK] Full MR2 - 1.66.605.2 - Froyo leaked MR2

[RUU] 1.13.605.7 Radio 1.16.00.0402 signed MR1

[ROM]Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_N V_8k_1.41_9k_1.64_release shipping firmware

[RUU] All known Mecha RUUs & OTAs (signed only) 5/16/2011

thunderbolt RUUs:

[ROM]RUU_Mecha_VERIZON_WWE_1.13.605.7_Radio_1.16.00.040 2w_1_NV_8k_1.41_9k_1.64

[ROM]RUU_Mecha_S_VERIZON_WWE_1.70.605.0_Radio_0.01.69.0 625r_NV_8K_1.41_9K_1.64

rooted OTAs(stock recovery and hboot removed):
flash these RUUs is you want to continue running a current,stock but rooted firmware
[ruu][rooted][MR1 aka OTA] CONFIRM Build Number: 1.13.605.7 Baseband: 1.16.00.0402w_1

[ROM] Official 1.70.605.0 MR2 OTA Deodexed Rooted Busybox Mirrors Added

*PLEASE NOTE: all the RUUs are available on xda. however,i have chosen to only include the ones that are considered safe,as per the security warning above. please do not go to xda and attempt to flash older RUUs without good reason... just because they are there and you can doesnt mean that you should.


*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.

 

[iAstonish]

Good idea! Thanks for the organized list of root methods. Could you add a poll for "best easy root method"?

 

[jcase]

I would advise people, unless you know how to recover your device from a failure on your own, do not do the one click/easy/scripts.

The root method is a little complex, and these applications are not quite ready to do it with a high enough success rate. (From judging the number of help requests we get in chat related to them).

http://forum.xda-developers.com/showthread.php?t=996616 is the safest, most successful method (and all others are based on it).

 

[scotty85]

i personally used the "easy root" method(the first to come out after manual root) and i thot it wasnt so "easy". the prollems i had were minor,with a couple PC reboots,unplugging the phone and replugging,and having to run each step multiple times among the "fixes" for the issues i had.

if i were to do it all again,i would do it the manual way,especially after watching some of the videos that are out,and practicing some adb commands on my eris.

i will try and track down links for some of the videos ive seen on setting up adb,and rooting the TB manually,and add those to the first post as well.

thanks for your input jcase.

 

[WormDoes]

Good idea, but I don't see many more how to root threads coming out that would warrant needing to constantly update this thread. I would think the only guide left to possibly come out would be unrEVOked.

 

[scotty85]

Good idea, but I don't see many more how to root threads coming out that would warrant needing to constantly update this thread. I would think the only guide left to possibly come out would be unrEVOked.

i agree completely. when i said id keep it updated,i just meant keep it current. this thread isnt going to change daily,or even weekly,but the methods will eventually be obsolete. in time we may only need a link to unrevoked,and nothing else.

but the current unroot methods may change,and i can keep adding the RUU links as they come out as well.

no biggie tho,if it doesnt get stickied we can still link to it when people ask... i just thot it would be handy to have the links in one spot,and might cut down on some of the "whats the best way to root,what should i do" questions

 

[ahoogst]

Great idea, scotty. I have a billion bookmarks related to rooting but this makes life much simpler.

 

[scotty85]

lol,i prolly have that many bookmarks as well. plus several files with roms,kernels,nand backups,ruus,etc.

 

[ahoogst]

I assume the tutorial videos are still up to date even with the OTA? I'm finished with my finals and have the time to root now wooo!

 

[scotty85]

I assume the tutorial videos are still up to date even with the OTA? I'm finished with my finals and have the time to root now wooo!

as far as the manual method,and its videos,yes. the original post for [ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 - xda-developers has been updated saying the method has been updated to inlclude the new OTA. the changes should be only to the files,and the modified RUU,the directions should have remained unchanged.

as far as the one click/easy root methods,i would avoid these unless you can confirm with the creator that the method has been updated for the 1.13.605.7 firmware.

 

[ridobe]

i personally used the "easy root" method(the first to come out after manual root) and i thot it wasnt so "easy". the prollems i had were minor,with a couple PC reboots,unplugging the phone and replugging,and having to run each step multiple times among the "fixes" for the issues i had.

if i were to do it all again,i would do it the manual way,especially after watching some of the videos that are out,and practicing some adb commands on my eris.

i will try and track down links for some of the videos ive seen on setting up adb,and rooting the TB manually,and add those to the first post as well.

thanks for your input jcase.

Everything stated about the manual method being the easiest/safest is true. I used the same "easy root" method and fumbled my way through but figured it out. I had to return my TB due to other issues. I unrooted (quiet easily) and rooted my new one using the original manual way by jcase all in about an hour.

 

[ahoogst]

I'm in the process of rooting using the manual method and while putting the downgrade RUU on my SD card the phone somehow changed back to charge only mode. I disabled/renabled USB debugging and turned disk drive back on. Should I start the root process over again or can I just resume from the last step?

Edit: The RUU didnt transfer all the way so I put it back on after reconnecting the TB and the transfer was successful. Can I just do the reboot bootloader step now?

Edit 2: Nevermind! I'm rooted and I'm making a nandroid right now before I flash BAMF 1.6.3!!

 

[scotty85]

I'm in the process of rooting using the manual method and while putting the downgrade RUU on my SD card the phone somehow changed back to charge only mode. I disabled/renabled USB debugging and turned disk drive back on. Should I start the root process over again or can I just resume from the last step?

Edit: The RUU didnt transfer all the way so I put it back on after reconnecting the TB and the transfer was successful. Can I just do the reboot bootloader step now?

Edit 2: Nevermind! I'm rooted and I'm making a nandroid right now before I flash BAMF 1.6.3!!

sorry i didnt get back to you sooner,im glad you figured it out. as was said to me: "congratulations! your cigar and jacket are on the table"

 

[ahoogst]

sorry i didnt get back to you sooner,im glad you figured it out. as was said to me: "congratulations! your cigar and jacket are on the table"

Ha thanks. I'm running Das Bamf 1.6.3 Remix right now and just getting everything up and running again. I was under the impression BAMF would debloat but I had to get rid of Blockbuster etc. manually with Titanium Backup. Is this normal?

 

[Deleted User]

I'm about to take the plunge and root my phone, but I don't know how to back up application data before root (which will wipe data, right?).

I don't want to lose all my Angry Bird stars!

I have a mix of regular android market and amazon market apps. What's the best way to back up all the application data?

Oh, and one more question: What actually gets wiped? my SD card, or just the internal memory?

Thanks in advance.

 

[scotty85]

unfortunately,there is no way to back your data up prior to rooting,that i know of. also unfortunately,the current root methods will wipe out your data.

as for what gets wiped,neither. both the internal phone storage and the SD card will be untouched,so any pics,video,music,etc. should still be intact after rooting.

what gets wiped is simply your personal data.

hope that helps

 

[Deleted User]

thanks for the reply, but I guess I'm still a little confused. What personal data gets deleted? Just SMS/MMS, contacts, call history? Or does it wipe out all apps and all app data too (is that considered "personal" data)?

I just want to know what to expect when I root.

 

[ahoogst]

thanks for the reply, but I guess I'm still a little confused. What personal data gets deleted? Just SMS/MMS, contacts, call history? Or does it wipe out all apps and all app data too (is that considered "personal" data)?

I just want to know what to expect when I root.

Apps and app data is wiped, unless an app has stuff stored on the SD card. For example, my Tiger GBC emulator stored roms/saves in the SD card which did not get erased. However, I did lose all my Angry Birds progress which is stored internally in the inaccessible internal Data directory. This data directory does be come accessible, but only after rooting which is when you can use Titanium Backup to backup your apps + app data. Hope that clears it up.

Edit: Also if you're like me and have 30+ apps to restore each time you might want to invest $6 for the Pro edition of Titanium Backup which can do zero-click restores. Considering how often new roms release/update it's probably worth it.

 

[Deleted User]

awww, balls.

Oh well, I still want to root. I'll just re-do all those levels. haha

Thanks for the info.

 

[fel2941]

Trying to reroot my phone here, and cant figure out where i put the push files. I try the command but i get

cannot stat 'psneuter' : no such file or directory. I downloaded all the stuff needed to do this, but the files are on my desktop. I cant find anywhere where it tells me where to put then to use the command

adb push psneuter /data/local/

 

[scotty85]

Trying to reroot my phone here, and cant figure out where i put the push files. I try the command but i get

cannot stat 'psneuter' : no such file or directory. I downloaded all the stuff needed to do this, but the files are on my desktop. I cant find anywhere where it tells me where to put then to use the command

adb push psneuter /data/local/

put them into whatever directory youre running the commands from. usually /tools or /platform tools.

another option would be to put the android-sdk-windows into your path,and then you can push files from a different folder. ie create a folder called "root files" or "flashables" or something like that,youll just have change to that directory when you open your command window

 

[fel2941]

All set, thanks!

 

[Familyguy1]

Thanks for stickying, been looking for this.

I still have the firmware that came with the phone( meaning I never updated to the crash-prone version), so if I still have the original firmware, could easy-root theoretically work?

 

[scotty85]

Thanks for stickying, been looking for this.

I still have the firmware that came with the phone( meaning I never updated to the crash-prone version), so if I still have the original firmware, could easy-root theoretically work?

i would think so. what i dont know is if the RUU files have been updated,so no telling what rooted firmware youd be running at the end of the process. jcases method will result in rooted mr1(1.13.605.7),but the easy root methods could result in rooted 1.12.605.9. if that makes sense.

as for becoming sticky,the thanks goes to a guide named "ocnbrze". he took the intiative to notice it,approach me for my thots,and then make it sticky.

 

[Familyguy1]

So the best option would be to go for Jcases? Alright, he was good on the Eris, so I can trust him with this