-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Thunderbolt Root/Unroot Thread
- Thread starter scotty85
- Start date
-
- Tags
- htc thunderbolt
unfortunately no... without the volume rocker you are back to wireless adb in step 3.
i can help you with that,if you want.
How every you could help that would be awesome...!!! I am ready to go whenever you have time.
scotty85
Extreme Android User
you dont have the command quite right:
your command:
adb push busybox/data/local/
should be:
adb push busybox /data/local/
the spaces seem insignifcant,but are important
try and copy the command from the thread,then paste it into the cmd promt,and see how the rest goes. i have to step out for a bit,but ill check in on you later
you dont have the command quite right:
your command:
adb push busybox/data/local/
should be:
adb push busybox /data/local/
the spaces seem insignifcant,but are important
try and copy the command from the thread,then paste it into the cmd promt,and see how the rest goes. i have to step out for a bit,but ill check in on you later
that little bit of help was all I needed to get it all done!! thanks so much...I think I had just been looking at all of it for so long that I wasn't pay attention to my mistakes in the script! Thanks again!!!
AlexOnVinyl
Member
If someone could please help me on my threads I've made for actually rooting my Thunderbolt - I'm a noob and would love some help. Please give me some walkthroughs. A lot of this is hard to keep up with coming from a noob perspective.
also, I'm running ubuntu linux.
also, I'm running ubuntu linux.
scotty85
Extreme Android User
there are directions in the OP to maually run fre3vo and then run revolutionary. there is a linnux download for revolutionary,and the fre3vo commands could prolly easily be modded to run from terminal in linux. use google to find some guides on getting the sdk set up on ubuntu if you dont allready have it
failing that,you can borrow a windows desktop or laptop and use the manual directions as-is,or use trter's tool. the downloads are small and unintrusive,and the process is quick.
AlexOnVinyl
Member
there are directions in the OP to maually run fre3vo and then run revolutionary. there is a linnux download for revolutionary,and the fre3vo commands could prolly easily be modded to run from terminal in linux. use google to find some guides on getting the sdk set up on ubuntu if you dont allready have it
failing that,you can borrow a windows desktop or laptop and use the manual directions as-is,or use trter's tool. the downloads are small and unintrusive,and the process is quick.
I'm going to be as honest and polite about this as possible, but seriously, these instructions aren't noob friendly and don't explain to me the process, all I've read are multiple ways of rooting a single phone - one is harder than the other and one requires you downgrade your phone. I'm upset as a new user that even the simplest of questions don't get answered but rather pointed to this thread or another stickied thread. Its upsetting and downright aggravating - These instructions don't really explain at all to someone new to rooting as to what is going on - and therefore resulting in bricks or loops.
In fact most of the help I've received here doesnt make me feel any better about rooting my phone, but rather worse and even more confused. Someone says "use Revolutionary" and someone else says "use miniadb_tb.zip" and gives a bunch of sdk commands to move files around.
If you're going to make a forum for helping with rooting - make something that caters to people who are stuck on trying to understand, not just throwing them into the pool and expecting them to doggie paddle to the edges.
scotty85
Extreme Android User
since were being honest,and i will try and be as polite as possible as well. the directions in the OP are as noob friendly as i can possibly make them. all you need to do is follow thes directions step by step to do it manually:
how to root 2.11.605.9/2.11.605.19 WITHOUT downgrading
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
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]if you have specific questions,id be happy to answer them,but your questions are all very broad,and im honestly not sure what youd like us to tell you. there is a wealth of information here on the forum if youre willing to spend some time browsing and reading.
if you do not want to use this manual method,trters tool is about as easy as it gets. i have not used it,but in another post he just to run it and press 1
i am truly sorry that you do not feel like youre being helped. as i mentioned, these directions are as noob friendly as i can make them,and i spend alot of time putting things together and keeping them updated. i point you here,as there is not anything different i can tell you.
rest assured that the above will not result in a brick or bootloop.
AlexOnVinyl
Member
since were being honest,and i will try and be as polite as possible as well. the directions in the OP are as noob friendly as i can possibly make them. all you need to do is follow thes directions step by step to do it manually:
how to root 2.11.605.9/2.11.605.19 WITHOUT downgrading
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
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]
if you have specific questions,id be happy to answer them,but your questions are all very broad,and im honestly not sure what youd like us to tell you. there is a wealth of information here on the forum if youre willing to spend some time browsing and reading.
if you do not want to use this manual method,trters tool is about as easy as it gets. i have not used it,but in another post he just to run it and press 1
i am truly sorry that you do not feel like youre being helped. as i mentioned, these directions are as noob friendly as i can make them,and i spend alot of time putting things together and keeping them updated. i point you here,as there is not anything different i can tell you.
rest assured that the above will not result in a brick or bootloop.
Okay then now how would I do this on an Ubuntu system? Why would I need to downgrade as stated above?
AlexOnVinyl
Member
I appreciate you taking the time out to explain it all to me, although I'm still a little confused, is it possible to do all this on an Ubuntu system? And if it's not needed to downgrade anymore then why are the options still there? Also, what's the difference between this way & trtr's tool?
scotty85
Extreme Android User
no where that i can see does it say you need to downgrade. the OP list it as an option,or alternative. if you run trters tool.or manually temp root you do not need to downgrade.
just to give you a lil more info,revolutionary does not work "out of the box" anymore. 2 firmware versions ago(2.11.605.5) the exploit it used was fixed. so this is why we do not say "just run revolutionary".
you need to give revolutionary a means of temp root(the directions i listed) oryou need to downgrade the older firmware. the way im recomending is the temp root,as the downgrade will wipe your data,and is possibly not even working with this latest firmware,anyway.
as far as suing ubuntu,im not 100% sure. i dont know the specifics,but basically:
-download the linux version of revolutionary
-install the android sdk
-figure out what slight differences there may be with the commands
- place fre3vo into the proper folder
-run the commands in terminal
when you get to the end,if you get the # as is described,then run the revolutionary program
sure you can do it on ubuntu. unfortunately,youre on your own to set up the android sdk and modify the commands slightly.
again,no where does it say you have to downgrade. it was one of t possible ways to be able to run revolutionary,as i described above. in the other thread,i reccomended you to forget having read about downgrades. the option is still there in case folks do not want to use adb and temp root. i actually am pretty sure the downgrade option will NOT work with the .19 firmware,but i cannot test. as soon as a user post up and says "i tried to downgrade and it failed" i will modify those directions.
for the most part. but there may be slight differences,and i do not know enuff about linux and ubunto to direct him.
Okay i figured out how to run revolutionary now i just dont know how to do the last step. flash the superuser 3.07 files linked on revolutionarys info page. How do you flash that?
scotty85
Extreme Android User
-download
-place on sd card
-boot to recovery
-wipe cache/dalvik cache
-install zip(choose the superuser file)
-reboot
So I recently acquired a Thunderbolt from a friend because it keeps getting stuck at HTC splash screen. I have tried to follow this method but cannot find my device when I try adb devices from the bootloader since I cannot get into android OS. Once I get into fastboot USB however, I am able to use fastboot devices to see my device.
Any one run into this before? Thanks in advance..
P.S also tried going into recovery, deleting data from bootloader and it takes me back to HTC screen. Anyone have the latest RUU.exe? In fastboot I can do fastboot oem rebootRUU and takes me to dark htc screen but it fails when I run executable..
Any one run into this before? Thanks in advance..
P.S also tried going into recovery, deleting data from bootloader and it takes me back to HTC screen. Anyone have the latest RUU.exe? In fastboot I can do fastboot oem rebootRUU and takes me to dark htc screen but it fails when I run executable..
scotty85
Extreme Android User
the phone is prolly on the latest software,2.11.605.19,for wich there is not an executable. you can verify by a 1.49.00.0406w_1 for the baseband in hboot.
if you had the 2.11.605.9 firmware,youd see a baseband of 1.48.00.0930w
if you are indeed on .19,your best bet is to run a PG05IMG in hboot. you can download fom here: Shipped ROMs
footballs folder is here: FileFactory Folder View - Mecha
if your baseband is not one of the above,you can find a list here: http://androidforums.com/thunderbol...ries-hboot-updated-4-18-12-a.html#post3104540
make sure the hboot is not htcdev unlocked. if so,it will need to be relocked to run an ruu(.exe or .zip)
holler if you have further questions
if you had the 2.11.605.9 firmware,youd see a baseband of 1.48.00.0930w
if you are indeed on .19,your best bet is to run a PG05IMG in hboot. you can download fom here: Shipped ROMs
footballs folder is here: FileFactory Folder View - Mecha
if your baseband is not one of the above,you can find a list here: http://androidforums.com/thunderbol...ries-hboot-updated-4-18-12-a.html#post3104540
make sure the hboot is not htcdev unlocked. if so,it will need to be relocked to run an ruu(.exe or .zip)
holler if you have further questions
realisticmusic
Lurker
I followed the stuff to the "T" and when I put in the beta key it stated: "Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
bla bla lemons bla bla
Waiting for fastboot..."
the phone went to the screen with the 3 android on skateboards at bottom. I tried to go and do the fastboot but it would say an error loading image...
ok, I just want to factory reset the phone (having issues anyways and saved all I want with My Backup Pro) but with superuser installed. My main thing is wipe phone, root phone, able to tether.
I just used the reset option on the skateboard screen and it just went to my regular home screen with my apps.
I have been reading forums and forums from site to site and so many different things. I thought I had it but nothing. I downloaded the PG05IMG that is "rooted" but dunno what to do with it if I even need it.
Any help would be great.
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
bla bla lemons bla bla
Waiting for fastboot..."
the phone went to the screen with the 3 android on skateboards at bottom. I tried to go and do the fastboot but it would say an error loading image...
ok, I just want to factory reset the phone (having issues anyways and saved all I want with My Backup Pro) but with superuser installed. My main thing is wipe phone, root phone, able to tether.
I just used the reset option on the skateboard screen and it just went to my regular home screen with my apps.
I have been reading forums and forums from site to site and so many different things. I thought I had it but nothing. I downloaded the PG05IMG that is "rooted" but dunno what to do with it if I even need it.
Any help would be great.
ninedragons
Newbie
I apologize in advance if this was posted in the wrong place, or if I should not link to apps in the Google Play Store (I didn't see anything in the rules), but I thought that this was well worth posting.
I was unrooting a friend's TBolt earlier for an insurance replacement (nothing to do with me rooting it and flashing custom ROMs on it for him, the screen cracked after it fell out of its case while he was running). I never had to unroot a TBolt, although I've rooted several for friends, so I didn't have the files that I needed to unroot. In the course of looking up info about unrooting a TBolt and getting it back to factory stock GB, I came across an app called "HTC Thunderbolt Restore" on the Google Play Store. It cost $1.99, but it was incredibly easy. I downloaded it, and ran it, and I can confirm that it most definitely worked beautifully, and it couldn't be any easier. It takes awhile for it to do everything it needs to do, maybe 15-20 minutes, but it did exactly what it was supposed to do; S-ON, no trace of the fact that it was ever rooted, and everything worked as it should.
For those who are having trouble finding the files to unroot, or don't want to go through the process, I highly recommend it.
The app and reviews can be seen here: https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5kYXJrc2xpZGUudGh1bmRlciJd
I didn't write the app or even heard of it until a few hours ago, and I only tried it once. So, if for some reason, it doesn't work for you, don't send me hate mail! Just thought I'd give anyone needing to unroot a heads-up that there is another option.
I was unrooting a friend's TBolt earlier for an insurance replacement (nothing to do with me rooting it and flashing custom ROMs on it for him, the screen cracked after it fell out of its case while he was running). I never had to unroot a TBolt, although I've rooted several for friends, so I didn't have the files that I needed to unroot. In the course of looking up info about unrooting a TBolt and getting it back to factory stock GB, I came across an app called "HTC Thunderbolt Restore" on the Google Play Store. It cost $1.99, but it was incredibly easy. I downloaded it, and ran it, and I can confirm that it most definitely worked beautifully, and it couldn't be any easier. It takes awhile for it to do everything it needs to do, maybe 15-20 minutes, but it did exactly what it was supposed to do; S-ON, no trace of the fact that it was ever rooted, and everything worked as it should.
For those who are having trouble finding the files to unroot, or don't want to go through the process, I highly recommend it.
The app and reviews can be seen here: https://play.google.com/store/apps/...1bGwsMSwyLDEsImNvbS5kYXJrc2xpZGUudGh1bmRlciJd
I didn't write the app or even heard of it until a few hours ago, and I only tried it once. So, if for some reason, it doesn't work for you, don't send me hate mail! Just thought I'd give anyone needing to unroot a heads-up that there is another option.
scotty85
Extreme Android User
tbolt2 contains adb,fastboot,and the files needed for them to work. transfer fre3vo into this folder,so adb,fastboot,and fre3vo are all in the same place.
Danielv561
Newbie
hi, i have 2012 htc TB, firmware 2.3.5, baseband ver: 2.15.00.01.15, kernel ver:2.6.35.10,
I wana do this right the 1st time, d/l revolutionary, htc driver, but link to new updated SU zip was bad, IDK if this is the file Kaosdroid-deb-8.00beta1-2 ??? If sum1 has correct SU zip 4 my cell please post it, next question my carrier is sprint which i have unlimited data plan so I wana root 4 free wifi hopspot but what rom do i need 2 get hopspot like Trev MOD etc? Lastly I dont have 2 do half root then full my cell is already for full root setup? Thank You all and Happy 4th of July!!!!!!!!!!
I wana do this right the 1st time, d/l revolutionary, htc driver, but link to new updated SU zip was bad, IDK if this is the file Kaosdroid-deb-8.00beta1-2 ??? If sum1 has correct SU zip 4 my cell please post it, next question my carrier is sprint which i have unlimited data plan so I wana root 4 free wifi hopspot but what rom do i need 2 get hopspot like Trev MOD etc? Lastly I dont have 2 do half root then full my cell is already for full root setup? Thank You all and Happy 4th of July!!!!!!!!!!
scotty85
Extreme Android User
Are you sure you have a thunderbolt? Not sure how you can be using a Verizon phone on sprint.
