Thunderbolt Root/Unroot Thread

scotty85 · September 23rd, 2011, 06:13 PM

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

for some extra info and "how to"s of rooting see [HOW TO] and some root terminology

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:
[ALL IN ONE] The HTC Thunderbolt Tool!
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

__________________________________________________ ________________________________
how to unroot

__________________________________________________ ________________________________

some other info

WormDoes · October 1st, 2011, 10:49 AM

Radios, Recoveries and HBOOT's

WormDoes · October 1st, 2011, 02:21 PM

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?id=com.ttxapps.wifiadb&feature=search_resu lt#?t=W251bGwsMSwyLDEsImNvbS50dHhhcHBzLndpZmlhZGIi XQ.. 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:

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

C:\Users\Scott>cd c:\tbolt

c:\tbolt>adb connect 192.168.1.68:5555
connected to 192.168.1.68:5555

c:\tbolt>adb devices
List of devices attached
192.168.1.68:5555       device


c:\tbolt>adb push busybox /data/local/
641 KB/s (1062992 bytes in 1.618s)

c:\tbolt>adb push hbooteng.nb0 /data/local/
620 KB/s (1048576 bytes in 1.649s)

c:\tbolt>adb shell
$ su
su
# chmod 777 /data/local/busybox
chmod 777 /data/local/busybox
# /data/local/busybox md5sum /data/local/hbooteng.nb0
/data/local/busybox md5sum /data/local/hbooteng.nb0
6991368ee2deaf182048a3ed9d3c0fcb  /data/local/hbooteng.nb0
# dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
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)
# /data/local/busybox md5sum /dev/block/mmcblk0p18
/data/local/busybox md5sum /dev/block/mmcblk0p18
6991368ee2deaf182048a3ed9d3c0fcb  /dev/block/mmcblk0p18
# exit
exit
$ exit
exit

c:\tbolt>adb reboot

scotty85 · October 1st, 2011, 03:34 PM

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

- 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-thunderbolt-custom-roms/gingerbreadrockv1-0-v1-1-(newest-gingerbread-leak)/

-minor GB OTA(2.11.605.19)
http://androidforums.com/thunderbolt-all-things-root/467448-updated-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 Thunderbolt Root/Unroot Thread 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/04/17/exclusive-download-build-2-11-605-19-for-the-htc-thunderbolt-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_Rad io_0.01.78.0906w_2__NV_8K_1.41_9K_1.64_release_219 938_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_Rad io_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_2268 79_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

rolly not flashable a vzw branded phone
1.01.1520.0 leak
FileFactory Premium

last and not least:
collection of shipped roms for thunderbolt(mecha)

scotty85 · October 1st, 2011, 03:42 PM

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:

cd c:\tbolt

you should see your promt in the window change to: c:\tbolt>
7)enter the follwing command:

Code:

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:

md5sums PG05IMG_no_hboot_2.11.605.9.zip

it may take a minute,but it should output 3e189b6c85ea7da1e26e12a5cd7b1ab0

9)

Code:

md5sums hboot_7630_1.05.0000_110719.nb0

output should be e1e330356ec5c889a92be1b5ef6c853d

10)

Code:

adb reboot bootloader

11)

Code:

fastboot devices

should output serial number

11a)

Code:

fastboot erase cache

12)

Code:

fastboot oem rebootRUU

13)

Code:

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

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:

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:

fastboot devices

assuming you see a serial number,then:

16)then:

Code:

fastboot reboot-bootloader

17)unlock revolutionary hboot:

Code:

fastboot oem mw 8d08ac54 1 31302E30

18)write 1.05.0000 hboot(md5 above matched,right?

)

Code:

fastboot flash hboot hboot_7630_1.05.0000_110719.nb0

19)then:

Code:

fastboot reboot-bootloader

20)then:

Code:

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:

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

C:\Users\Scott>cd c:\tbolt

c:\tbolt>adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
HT12CS012936    device


c:\tbolt>md5sums PG05IMG_no_hboot_2.11.605.9.zip

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>md5sums hboot_7630_1.05.0000_110719.nb0

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>adb reboot bootloader

c:\tbolt>fastboot devices
HT12CS012936    fastboot

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

c:\tbolt>fastboot oem rebootRUU
                              ... OKAY [  0.220s]
finished. total time: 0.221s

c:\tbolt>fastboot devices
HT12CS012936    fastboot

c:\tbolt>fastboot flash zip PG05IMG_no_hboot_2.11.605.9.zip
     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>fastboot devices
HT12CS012936    fastboot

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

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

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

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

c:\tbolt>fastboot reboot
                     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:

c:\tbolt>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.04.2000 <-this should say 1.05.0000
INFOversion-baseband: 1.48.00.0101w <-this should be 1.48.00.0930w 
INFOversion-cpld: None
INFOversion-microp: /
INFOversion-main: 2.10.605.1 <-this should be 2.11.605.9
INFOserialno: HTxxxxxxxx
INFOimei: 355195000000017
INFOproduct: mecha
INFOplatform: HBOOT-7630
INFOmodelid: PG05*****
INFOcidnum: 11111111 <- this should be VZW_001
INFObattery-status: good
INFObattery-voltage: 4112mV
INFOpartition-layout: Generic
INFOsecurity: off <-this should say on
INFObuild-mode: ENG <-this should be SHIP
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

parrc · October 3rd, 2011, 03:33 PM

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.

scotty85 · October 3rd, 2011, 04:20 PM

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*

parrc · October 3rd, 2011, 05:58 PM

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

Yeahha · October 3rd, 2011, 06:44 PM

Quote:

Originally Posted by parrc

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

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 · October 3rd, 2011, 07:16 PM

Awesome. Glad you got it working

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

fixxxer1022 · October 3rd, 2011, 07:49 PM

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.

Yeahha · October 3rd, 2011, 07:54 PM

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?

scotty85 · October 3rd, 2011, 08:20 PM

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

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 · October 3rd, 2011, 08:34 PM

Quote:

Originally Posted by scotty85

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

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.

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

fixxxer1022 · October 3rd, 2011, 08:36 PM

Quote:

Originally Posted by Yeahha

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?

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

Yeahha · October 3rd, 2011, 08:52 PM

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?

fixxxer1022 · October 3rd, 2011, 08:58 PM

Quote:

Originally Posted by Yeahha

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?

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.

Yeahha · October 3rd, 2011, 09:08 PM

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

scotty85 · October 3rd, 2011, 09:25 PM

Quote:

Originally Posted by fixxxer1022

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.

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.

Quote:

Originally Posted by Yeahha

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

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.

fixxxer1022 · October 3rd, 2011, 09:31 PM

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.

scotty85 · October 3rd, 2011, 09:38 PM

Quote:

Originally Posted by fixxxer1022

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?

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.

Quote:

Originally Posted by fixxxer1022

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

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.

Yeahha · October 3rd, 2011, 09:41 PM

Quote:

Originally Posted by fixxxer1022

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?

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.

Quote:

Originally Posted by fixxxer1022

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

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.

fixxxer1022 · October 3rd, 2011, 09:47 PM

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

fixxxer1022 · October 3rd, 2011, 09:49 PM

Quote:

Originally Posted by Yeahha

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

Yeah htc needs to rectify this and soon.

Yeahha · October 3rd, 2011, 09:52 PM

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.

fixxxer1022 · October 3rd, 2011, 10:18 PM

Quote:

Originally Posted by Yeahha

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.

I did root with revolutionary on my tbolt, sorry if i wasnt clear on that. Or were you talking about the charge?

Yeahha · October 3rd, 2011, 10:25 PM

I was talking about the charge, it looks like the root process is a little more difficult than revolutionary but most things are now. Yet it doesn't look too daunting, a lot like the older process we had to root the bolt.

fixxxer1022 · October 4th, 2011, 09:18 AM

worked flawless, im s-on, unrooted and now running the gb ota.... thanks guys!

hope to see you all again when the prime hits!

Yeahha · October 4th, 2011, 09:32 AM

Glad it worked for you, enjoy the charge man!

dwbrewer · October 4th, 2011, 09:38 AM

Question from a root noob, is it possible to root after the GB is applied? I have the craptastic GB update applied. I have a service ticket open with Verizon and can get a replacement without GB.

scotty85 · October 4th, 2011, 09:42 AM

You don't need a replacement. Revolutionary will root the 1.05.0000 locked gb hboot just fne

fixxxer1022 · October 4th, 2011, 09:59 AM

stupid question but will z4root or gingerbreak work on the tbolt as a temp solution without having to go s-off? now that im s-on i might want to temp root until my charge gets here.

Yeahha · October 4th, 2011, 10:08 AM

No it won't.

scotty85 · October 4th, 2011, 10:29 AM

1)run revolutionary
2)install clockwork and superuzer
3)remove revoluinary hboot
4) flash mr2 files when charge arrives

fixxxer1022 · October 4th, 2011, 10:30 AM

Quote:

Originally Posted by Yeahha

No it won't.

well that sucks but oh well.

fixxxer1022 · October 4th, 2011, 10:31 AM

Quote:

Originally Posted by scotty85

1)run revolutionary
2)install clockwork and superuzer
3)remove revoluinary hboot
4) flash mr2 files when charge arrives

naw im cool ill just stay stock for a day or two i guess.

jmc55 · October 5th, 2011, 07:23 PM

wow, you guys sure have put alot of time into this...and even with the step by step instructions i'm lost. my son helped me root my hero before i switched to the tb but he's recently joined the air force and is in bootcamp with no tie to the outside world for a while. argh! i'll keep looking at it and hope to eventually get rooted.

Yeahha · October 5th, 2011, 07:36 PM

Quote:

Originally Posted by jmc55

wow, you guys sure have put alot of time into this...and even with the step by step instructions i'm lost. my son helped me root my hero before i switched to the tb but he's recently joined the air force and is in bootcamp with no tie to the outside world for a while. argh! i'll keep looking at it and hope to eventually get rooted.

With revolutionary it is pretty easy to root, the explanations may seem harder than they actually are. What parts of the process are causing issues for you

jmc55 · October 6th, 2011, 06:32 PM

Quote:

Originally Posted by Yeahha

With revolutionary it is pretty easy to root, the explanations may seem harder than they actually are. What parts of the process are causing issues for you

nothing yet...i'm afraid of starting, getting hung up, then having no phone. i will jump into it this weekend. if i get stuck i'll know someone is standing by to assist.

thanks for responding.

Yeahha · October 6th, 2011, 06:43 PM

No problem, I like helping here. If you were to post here with an issue and not get a response quick enough (if you have a problem in the middle of rooting) then you can also use IRC to get answers

jmc55 · October 6th, 2011, 07:47 PM

Quote:

Originally Posted by Yeahha

No problem, I like helping here. If you were to post here with an issue and not get a response quick enough (if you have a problem in the middle of rooting) then you can also use IRC to get answers

IRC? see, i'm screwed! lol

Yeahha · October 6th, 2011, 07:58 PM

Internet Relay Chat

http://chat.andirc.net:9090/?channels=#thunderbolt

I don't think you should have any real issues with revolutionary, if you come into any post them in this thread, if you don't get a reply (I am rather inactive on the weekends but other people are more active) feel free to PM scotty85, WormDoes, or me, You can also try the IRC I linked as well but I promise you will get help if you have any issues.

jtb199 · October 9th, 2011, 10:49 AM

Quick question...

I rooted...all went well...

So I want to un-root...when I do will I lose all my data?...

scotty85 · October 9th, 2011, 10:59 AM

the short answer is yes,if you want to get rid of the su app and binary by flashing an ruu,then you will lose data.

how did you root,and why do you want to unroot?

if you just want to recieve an OTA,then you can flash a stock mr2 rom,flash the stock mr2 recovery,and thats all you need to do.

if you need to return for warranty purposes,then thats a different story. but in that case it wont really matter if you lose your data or not

jtb199 · October 9th, 2011, 11:18 AM

Quote:

Originally Posted by scotty85

the short answer is yes,if you want to get rid of the su app and binary by flashing an ruu,then you will lose data.

how did you root,and why do you want to unroot?

if you just want to recieve an OTA,then you can flash a stock mr2 rom,flash the stock mr2 recovery,and thats all you need to do.

if you need to return for warranty purposes,then thats a different story. but in that case it wont really matter if you lose your data or not

Thanks for the reply...

I was going to try some different ROMS...I seen there was a ROM that didn't wipe your data...it was Shifts3ns3 by Droidth3ory...but can't seem to find the ROM...the link is dead?...

So I decided to say the heck with it and un-root so I would be able to receive the OTA updates...but didn't realize un-rooting would cause the data lose

Sorry...kinda of a noob here...

Anyway...I started the un-root process and have the Revolutionary gone in hboot but have s-off...

Any recommendations what to do now?...

I really don't want to lose my data and rebuild my phone

Thanks again...

scotty85 · October 9th, 2011, 11:34 AM

Quote:

Originally Posted by jtb199

Thanks for the reply...

I was going to try some different ROMS...I seen there was a ROM that didn't wipe your data...it was Shifts3ns3 by Droidth3ory...but can't seem to find the ROM...the link is dead?...

So I decided to say the heck with it and un-root so I would be able to receive the OTA updates...but didn't realize un-rooting would cause the data lose

Sorry...kinda of a noob here...

Anyway...I started the un-root process and have the Revolutionary gone in hboot but have s-off...

Any recommendations what to do now?...

I really don't want to lose my data and rebuild my phone

Thanks again...

are you on mr2 now? (1.70.605.7) double check your firmware version,and if its that,you should be safe to go ahead and flash the mr2 recovery,then the "PG05IMG_hboot_only_1.04.0000" file. all your data will be intact,and youll be stock except for the su app and binary. just delete the superuser app and you can consider yourself unrooted.

the recovery link can be found on the thread linked in the 2nd post. you willl want to use:
MR2: http://www.multiupload.com/PB5F6G7C8Q
md5: a3320797390e3d746a67fda915854b16

so to recap:
1)flash stock recovery
2)flash stock hboot
3)delete superuser app

unrooted

jtb199 · October 9th, 2011, 11:38 AM

Quote:

Originally Posted by scotty85

are you on mr2 now? (1.70.605.7) double check your firmware version,and if its that,you should be safe to go ahead and flash the mr2 recovery,then the "PG05IMG_hboot_only_1.04.0000" file. all your data will be intact,and youll be stock except for the su app and binary. just delete the superuser app and you can consider yourself unrooted.

I assume I am?...I have the latest OTA that was pulled...

Sorry...seen where you updated your post...

So what files do I need to un-root without losing data...

I have the one you posted...now what?...

Sorry for having to hold my hand thru this...

Nevermind...I think I got it...I flashed the two files and have s-on...so i'm good to go with any OTA's correct?...

And one last thing...for instance...when I received the OTA that got pulled when in a call I occasionally hear a "chirp" sound...is there anyway I can flash a different radio now?...

scotty85 · October 9th, 2011, 06:28 PM

Quote:

Originally Posted by jtb199

I assume I am?...I have the latest OTA that was pulled...

whaaaa

Quote:

Originally Posted by jtb199

Nevermind...I think I got it...I flashed the two files and have s-on...so i'm good to go with any OTA's correct?...

given the above statement,i have no idea. since you were in too big of a hurry to wait for an answer,or double check your firmware number,you have inadvertantly flashed froyos stock hboot and recovery with gingerbread firmware. i *think* youre ok? but like i said,i have no idea for sure. i cannot reccomend you stay this way without having tested the situation myself,or knowing more about how the recoverys jive with the rest of the firmware.

*prolly* nothing bad will happen,but its quite possible to end up with anything from a failed update to a brick when the OTA hits.

next time i reccomend you not be so anxious when messing with something as important as your bootloader and stock recovery.

Quote:

Originally Posted by jtb199

And one last thing...for instance...when I received the OTA that got pulled when in a call I occasionally hear a "chirp" sound...is there anyway I can flash a different radio now?...

no. not with s-on,and its one of the big reasons that you should have left your revolutionary hboot alone. it will not affect your ability to recive OTAs(ive done it),and it leaves the door open for you to have control over things like this when you want it.

ideally,you should have waited for me to get home this eveing(ive been out of town),so i could pull a recovery from the 2.11.605.3 RUU and upload it for you. you could have flashed it,deleted superuser,and been good to go.

at this point,id reccomend that you reroot with revolutionary. wait for a recovery that matches your firmware(later this eveing),then flash it. the 1.05.0000 hboot is in the hboots + recoveries thread allready,if you really feel you need to get back to s-on,but id pretty strongly reccomend not to flash your hboot unneccesarily,and leave the revolutionary one in place.

wether or not your still interested,th3ory roms are here: HTC Thunderbolt Developer Forum you will have to register to download. sorry i didnt get you this information earlier,its been a busy few days and i havent been on the forum as much.

edit: here is the recovery that matches your 2.11.605.3 firmware(double check settings/about phone before flashing):

http://www.multiupload.com/42LE96JFMU
PG05IMG-2.11.605.3-stock-recovery.zip a3f6155023f3c928d0cd229516a441e1

jtb199 · October 9th, 2011, 09:20 PM

Quote:

Originally Posted by scotty85

whaaaa

given the above statement,i have no idea. since you were in too big of a hurry to wait for an answer,or double check your firmware number,you have inadvertantly flashed froyos stock hboot and recovery with gingerbread firmware. i *think* youre ok? but like i said,i have no idea for sure. i cannot reccomend you stay this way without having tested the situation myself,or knowing more about how the recoverys jive with the rest of the firmware.

*prolly* nothing bad will happen,but its quite possible to end up with anything from a failed update to a brick when the OTA hits.

next time i reccomend you not be so anxious when messing with something as important as your bootloader and stock recovery.

no. not with s-on,and its one of the big reasons that you should have left your revolutionary hboot alone. it will not affect your ability to recive OTAs(ive done it),and it leaves the door open for you to have control over things like this when you want it.

ideally,you should have waited for me to get home this eveing(ive been out of town),so i could pull a recovery from the 2.11.605.3 RUU and upload it for you. you could have flashed it,deleted superuser,and been good to go.

at this point,id reccomend that you reroot with revolutionary. wait for a recovery that matches your firmware(later this eveing),then flash it. the 1.05.0000 hboot is in the hboots + recoveries thread allready,if you really feel you need to get back to s-on,but id pretty strongly reccomend not to flash your hboot unneccesarily,and leave the revolutionary one in place.

wether or not your still interested,th3ory roms are here: HTC Thunderbolt Developer Forum you will have to register to download. sorry i didnt get you this information earlier,its been a busy few days and i havent been on the forum as much.

edit: here is the recovery that matches your 2.11.605.3 firmware(double check settings/about phone before flashing):

Multiupload.com - upload your files to multiple file hosting sites!
PG05IMG-2.11.605.3-stock-recovery.zip a3f6155023f3c928d0cd229516a441e1

Thanks for your help...

And agreed...I did jump the gun...

My phone under info under about phone is...

software 2.11.605.3

PRI Version 1.41_002, 1.64_002

Don't know if you need anymore inf but that's what I got...

If you need anymore info please let me know...

Should I go ahead and flash the recovery you posted?...

Again...thank you...

scotty85 · October 9th, 2011, 09:35 PM

Quote:

Originally Posted by jtb199

Thanks for your help...

And agreed...I did jump the gun...

My phone under info under about phone is...

software 2.11.605.3

PRI Version 1.41_002, 1.64_002

Don't know if you need anymore inf but that's what I got...

If you need anymore info please let me know...

Should I go ahead and flash the recovery you posted?...

Again...thank you...

you are quite welcome,im glad to help.i didnt mean to pick on you,but i wanted to get the point across for folks who read this in the future.

yes,id reccomend to flash the recovery i just posted. it matches your firmware version above

you will have to reroot with revolutionary first,as the s-on hboot will not let you flash the stock recovery. sounds a lil ironic,i know,but just becasue its stock doesnt mean the s-on will flash it. s-on only flashes "signed and approved by htc" files.