Root Thunderbolt Root/Unroot Thread

[otter]

Thanks! Verified

 

[Shine 52]

glad you got it. for others that see this, the fix would be to remove PG05IMG from the sd card. you can do this by booting the phone normally,then mount sd card as disc drive to pc,or by using a file manager.

in the event of a non working phone,simply put the sd into a card reader.

so are ya re-rooted?

Why yes I am and am running Thundershed 1.3 and I have to say, it's pretty slick looking, especially w/ the ICS theme.. Gotta figure out my radio situation though, I don't think I'm on what I was.

I will say I used the HTC Thunderbolt Restore App to un-root and it worked like a charm.

 

[madmadmad]

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)

how do i do this part?

nevermind. literally just copied and pasted the fre3vo into the other folder. everything works now rooted once again.

Where is the tbolt2 folder and how do i use adb/fastboot to transfer fre3vo into it....

 

[scotty85]

Where is the tbolt2 folder and how do i use adb/fastboot to transfer fre3vo into it....

have you read the original post? this is the first step:

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

you do not use adb or fastboot to trasnfer fr3evo to tbolt2.

steps 1-4 are explaining as clearly as i can where the files come from and what you need to do... you need to download the tbolt2 .zip file. unzip it,move it to the root of C on your computer. download the dhddowngrade and move fre3vo by any means that you are comfortable(copy/paste,drag/drop,right click/send to) it literally does not matter how you move fre3vo,as long as you end up with the tbolt2 folder on the root of your computers C drive with fre3vo inside of it.

try going back to the orginal post,and carefully follow the driections there,and we can go from there with whatever you are still confused with.

 

[madmadmad]

have you read the original post? this is the first step:


you do not use adb or fastboot to trasnfer fr3evo to tbolt2.

steps 1-4 are explaining as clearly as i can where the files come from and what you need to do... you need to download the tbolt2 .zip file. unzip it,move it to the root of C on your computer. download the dhddowngrade and move fre3vo by any means that you are comfortable(copy/paste,drag/drop,right click/send to) it literally does not matter how you move fre3vo,as long as you end up with the tbolt2 folder on the root of your computers C drive with fre3vo inside of it.

try going back to the orginal post,and carefully follow the driections there,and we can go from there with whatever you are still confused with.

Man im dumb, I figured it out, i missed the part where i was supposed to UNZIP the zip, for some reason i thought it stated that you left it in the zip.


Well i ran revolutionary and now im sitting at a white screen with 3 androids on skateboards

revolutionary closed and said it was successful but i didnt flash any files (i dont know how to do that)

so how do i "flash" the superuser files onto it

EDIT: Okay so i got everything working, had superuser on an everything, then i tried installing infectedROM

i used the same recovery method i used to get superuser, and it said it went through correctly, but then when i went to REBOOT or whatever, it didnt reboot, so i tried turning it on and now it keeps getting stuck on the white HTC screen, so i tried removing the battery and turning it back on but that doesnt help at all

EDIT EDIT: I tried flashing another ROM after doing a data/factory reset, and im still not having any luck, my phone boots up now, but it always goes to the revolutionary boot screen (black one, not the white one) the rom was ThunderShed v1.4

 

[rolltidedad]

When downloading the PG05IMG files to my PC in order to unroot my TB, will I need to unzip the folder before transferring it to my phone and flashing it in hboot?

The reason I ask this is because I transferred over the unzipped file, and when I tried to verify the md5 checksum through Scary Alien, I get the following message:

"Nandroid Verification Failure.

PG05IMG.zip: 129 lines read, 0 existing files, 129 non-existent files

Could not verify any files in the '/mnt/sdcard' directory.

The selected file does note appear to be formatted like an nandroid.md5 file.

[duration: 0.303 secs]

 

[rolltidedad]

When downloading the PG05IMG files to my PC in order to unroot my TB, will I need to unzip the folder before transferring it to my phone and flashing it in hboot?

The reason I ask this is because I transferred over the unzipped file, and when I tried to verify the md5 checksum through Scary Alien, I get the following message:

"Nandroid Verification Failure.

PG05IMG.zip: 129 lines read, 0 existing files, 129 non-existent files

Could not verify any files in the '/mnt/sdcard' directory.

The selected file does note appear to be formatted like an nandroid.md5 file.

[duration: 0.303 secs]

 

[scotty85]

no,you will leave the file zipped up.

sorry about the slow download speads,ill work on getting another mirror besides multiupload,but thats the best i can do at the moment.

 

[meinbeast]

So I have software version .9. Before I found the start of this thread I downloaded and put .5 on my device root as a zip and renamed the file pg05img.

I went through the process to flash with hboot and revert back to .5. I did that with no issues along the way. However my software did not update, its still at .9. After many many failed attempts I gave up and began searching again, when I cam across this thread to root on software version .9.

Do I now need to delete the pg05img.zip file off my device root??????


After I input all the commands and i then use revoutionary I successfully gain root!!! But after that what the heck do I do? ? I am able to select bootloader but after that I can move up and down the menu with the volume rocker. The phone automatically boots back up with pg05img

do I then delete pg05img? do I scroll down to recovery? I dont know whats next...thanks for the help!

 

[scotty85]

yes,by all means delete PG05IMG from your sd card. you should always delete them after they flash,as they will fudge you up if youre not booting and need to get to recovery to fix something. never leave them just hanging around on your sd card. if you wish to keep them on your sd,hide them inside a folder,or rename them.

after you gain temp root and run revolutionary,you will be s-off. you can let revolutionary install clockwork recovery,then you can boot into hboot,select recovery,and get to clockwork.

use clockwork to flash superuer 3.0.7 that you have downloaded from revolutionarys info page and placed on the root of your sd card prior.

its also not a bad idea to use clockwork to make a nandroid backup of your stock,unrooted rom before flashing the superuser zip.

hope that helps

 

[Wampa1]

Hey. I just recently found this forum and I had a quick question. I need to unroot to send my phone in after a power button failure. I rooted with the original auto root method and am running CM7 with the latest.605.9 radio. Is it as simple as flashing the RUU for 605.9, or is there something else I must do to get S-On? I've been getting conflicting answers on other forums. Thanks!

 

[scotty85]

everything on the first page has been updated for 2.11.605.9,sir. this is the safest way IMO,to return to stock,as simply running an RUU overtop of custom firmware may thru a security warning,wich should be recoverable by re-running the RUU,but sometimes not,in wich case youre up a creek without a paddle until new RUUs come out

installing the firmware first,the hboot second always works out and gets you back to stock without risking being stuck in bootloader with a security warning

if you rooted with revoutionary,youll need to remove the permanent hboot to send the phone back to vzw,those directions are there too.

so my advice would be to just follow directions on the first page. read thru them first,holler if youh ave questions

 

[Wampa1]

everything on the first page has been updated for 2.11.605.9,sir. this is the safest way IMO,to return to stock,as simply running an RUU overtop of custom firmware may thru a security warning,wich should be recoverable by re-running the RUU,but sometimes not,in wich case youre up a creek without a paddle until new RUUs come out

installing the firmware first,the hboot second always works out and gets you back to stock without risking being stuck in bootloader with a security warning

if you rooted with revoutionary,youll need to remove the permanent hboot to send the phone back to vzw,those directions are there too.

so my advice would be to just follow directions on the first page. read thru them first,holler if youh ave questions

Sounds good. I wasn't sure if I had to do it that way because I read through a conversation on page 5 where you directed someome to do that. Now I'll unroot the old phone and root the new one today. Thanks!

 

[scotty85]

Sounds good. I wasn't sure if I had to do it that way because I read through a conversation on page 5 where you directed someome to do that. Now I'll unroot the old phone and root the new one today. Thanks!

i may recomend different things for different situations. for example,"im selling a phone i want to make it s on and stock" i try and encourage folks to leave the phone s-off.

phone is broken and goin back to vzw,then it needs to be s-on

if you want to quote a particular post,i can tell you the logic that i used to recomend whatever i did

 

[Wampa1]

i may recomend different things for different situations. for example,"im selling a phone i want to make it s on and stock" i try and encourage folks to leave the phone s-off.

phone is broken and goin back to vzw,then it needs to be s-on

if you want to quote a particular post,i can tell you the logic that i used to recomend whatever i did

It was somewhere earlier in the thread, I can't seem to find it now. I flashed them both and ended up back on stock S-On so I think it's ready to send back. Thanks! I have my fingers crossed this time that my phone won't break, I sent in my original one for a headphone jack connection problem and it's funny that the replacement phone broke on the exact 1 year anniversary of buying it. Now on to rooting the replacement.

 

[BadEvilPenguin]

A World of Thanks to Scotty85 and a Few Notes after my SUCCESS using the method posted by scotty85 in "Thunderbolt Root/Unroot Thread" -Sept 23 2011

Device: HTC Thunderbolt (Verizon) 2.11.605.9
Method: Revolution with miniadb_tbolt2 to counter the 2.11.605.9 patches.

Prelim Advice: I recommend doing this through a laptop with sufficient battery charge AND on AC power -if power goes out, you still might be able to complete the process on battery power.

Now that it worked, here are some additional details I came across during the process. Hope this helps.

1) Turn off Realtime Virus Protection and Firewall - for me, Bitdefender flagged some of the Revolution and mini-adb_tbolt2 routines as malicious and blocked them.

2) The last step, where Revolution displays "Installing Recovery over Fastboot", may end without notification. The video shows a "Success" notification and the window remains open. For me, the window closed after completing the install. Not a real problem, but it did cause me, the noob, to waste time running back through the process because I thought it failed.

3) When attempting to uninstall certain stock apps like Tunewiki and the VCast crap, I had to uninstall updates through the Settings->Applications before the removal would take affect.

In closing, I will say that although I have 20 years of hardware, software, and programming experience, I was nervous as hell to try this. After all, one mistake could brick my new phone. HOWEVER, I was absolutely amazed at how easy this process was. If you give yourself an hour or so of no distractions, read through the process a few times before you begin, and don't rush, then you will end up with the same gitty elation you get when buy a new phone.

...Albeit no new stock phone can match the thrill and satifaction you get from the unleashed power and freedom of a rooted phone.

Thanks

 

[scotty85]

cool! im glad it was helpful

 

[doowop0593]

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 http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html

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

and now,on with the info. enjoy


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

see this page for info:
Revolutionary

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

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

feel free to do wichever is most comfortable
__________________________________________________________________________________
how to root 2.11.605.9/2.11.605.19 WITHOUT downgrading

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

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

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

3)download DHD Downgrade folder

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

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

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

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

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

adb push fre3vo /data/local/tmp

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

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

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

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

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

youre done


heres what youll see in the command window(red are my inputs,blue are just additional comments):

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

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

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


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

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

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

c:\tbolt2>[COLOR="red"]adb shell[/COLOR]
# [COLOR="Blue"]<-indicates that you have temp root access[/COLOR]

__________________________________________________________________________________
how to unroot
the revolutionary method of rooting uses a sneeky hboot exploit,and replaces your stock 1.04.0000 or 1.05.0000 bootloader with a modified permanent hboot. it not only gives you all the same fashboot flash abilities as the original engineering bootloader,but it very effectively blocks other hboots for overwriting it. its good,as you will remain s-off if you accidentally flash a full RUU,or accept an OTA,but makes it a little trickier to remove.

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

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

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

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

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

Setting up adb and removing the permanent hboot if youve never used adb before
1)if you no longer have the htc drivers that you installed when rooting with revolutionary,download them again from here on revolutionarys website.
2)next download *link removed (mirror)to somewhere convenient that youll be able to find it,like your desktop,or a "downloads" folder. it contains the old eng 1.40.2000 s-off hboot,and the bare minumum tools to install it.
3)the following directions were using windows 7 and chrome browser. other OS may be slightly different-the end result is you want unzipped,inside tbolt folder to be on the root of your C: drive.
-find the tbolt.zipdownload
-click on tbolt.zip download and open it.
-inside tbolt.zip,there is a folder labled tbolt. drag it to the root of C:. inside tbolt is the unpermanent hboot and some adb tools.
4) charge your Thunderbolt to 100%
5)click on then "start" bubble in the lower left corner of your screen. type "command" in the search window and hit enter. this will open a small black command window.
6)enter the following command(by typing or copy/paste):

cd c:\tbolt

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

md5sums hbooteng.nb0

check the output on the command window. THIS IS VERY IMPORTANT. the command must equal exactly 6991368ee2deaf182048a3ed9d3c0fcb if it does not,STOP!. delete the tbolt.zip download,and the unzipped tbolt folder from C:,re download and try it again. again,do not procede if the output in your command number does not equal it exactly.
8)once the number matches,you can continue. copy and paste the following codes into the command window:

adb devices

the output should be your phones serial number

now enter:

adb reboot bootloader

this will cause your phone to boot into FASTBOOT mode,wich is a white screen with colored letters.

now enter:

fastboot devices

the result again,should be your phones serial number.

9) now youre ready to enter the command to unlock the permanent hboot and flash the new,non permanent one.
to unlock,enter:

fastboot oem mw 8d08ac54 1 31302E30

write the new hboot:

fastboot flash hboot hbooteng.nb0

if you select bootloader at this point from the fastboot menu, youll still see the permanent s-off hboot,so select reboot with the volume rocker and power button and let the phone reboot. after it boots,you can adb reboot bootloader again,or power off, then power on/vol down and check that your pink "UNLOCKED" or "REVOLUTIONARY" is gone and you have the old 1.49.2000 bootloader.

here is what you should see in the command window,the red are my inputs:

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

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

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

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

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

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


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

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

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

c:\tbolt>

Putting current stock firmware and s-on back onto the phone

after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1)*link removed PG05IMG_no_hboot_2.11.605.9
mirror: https://rapidshare.com/#!download|854p1|2281873735|PG05IMG_no_hboot_2.11.605.9.zip|462614
md5: 3e189b6c85ea7da1e26e12a5cd7b1ab0
2)*link removed PG05IMG_hboot_ONLY_2.11.605.9.zip
mirror:PG05IMG_hboot_ONLY_2.11.605.9.zip
md5: d26b3253358407d459c654e6729a39ca

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

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

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

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

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

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

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


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

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

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

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

I have followed the TUTs to the wire, and I still keep running into this problem. While waiting for the cmd to finish I'll see "Potential exploit area found at address f9f0ba00:600. Payload verification failed." what does this mean and what im i suppose to do now? Please help please

 

[scotty85]

I have followed the TUTs to the wire, and I still keep running into this problem. While waiting for the cmd to finish I'll see "Potential exploit area found at address f9f0ba00:600. Payload verification failed." what does this mean and what im i suppose to do now? Please help please

not sure what that means. i tried it,and it worked for me on 2.11.605.19.

make sure you dont have htc sync,pda net,or anything else capable of interacting with your phone running.

maybe try re-downloading the DHD downgrade folder,maybe fre3vo is just corrupt?

 

[scotty85]

OP updated with file to unroot to 2.11.605.19

 

[bluelantern116]

Hello again Android Forums,

I am currently having some issues with my rooted Thunderbolt, due to the 2.11.605.19 update. My phone wants to update, but a green android with an ! mark appears on my phone overnight, draining my battery. Is there any way to update my phone without unrooting or wiping out my memory? If not, then how do I stop my phone from trying to update every day or so (it is getting really annoying?) Lastly, if there is a way to update my phone under these conditions, does it work in general for any future updates?

Thanks,
Bluelantern116

 

[scotty85]

Hello again Android Forums,

I am currently having some issues with my rooted Thunderbolt, due to the 2.11.605.19 update. My phone wants to update, but a green android with an ! mark appears on my phone overnight, draining my battery. Is there any way to update my phone without unrooting or wiping out my memory? If not, then how do I stop my phone from trying to update every day or so (it is getting really annoying?) Lastly, if there is a way to update my phone under these conditions, does it work in general for any future updates?

Thanks,
Bluelantern116

best way would be to flash jrockers rooted stock 2.11.605.19 rom. put the rom onto your sd via a card reader,or by mounting usb storage in recovery.

wipe cache,dalvik cache

do not wipe data/factory reset and you will not lose data or settings

afterward,you can update the radio as a PG05IMG

 

[bluelantern116]

best way would be to flash jrockers rooted stock 2.11.605.19 rom. put the rom onto your sd via a card reader,or by mounting usb storage in recovery.

wipe cache,dalvik cache

do not wipe data/factory reset and you will not lose data or settings

afterward,you can update the radio as a PG05IMG

Excellent, so is the rom you mentioned above found on the fourth post of this thread? If so, which one, because I see several of them that say 2.11.605.19. Thanks for the response

Bluelantern116

 

[scotty85]

it would be the one in the "rooted stock roms" section. its also just a couple posts from the top of the forum. heres a direct link: http://androidforums.com/thunderbol...ted-5-20-12-rooted-ota-2-11-605-19-files.html

 

[OMGPizzaParty]

Hi, guys. Long time lurker, first time poster. Thank you all so much for the info--this has been incredibly educational and helpful. I have a situation with my rooted TBolt and don't want to do anything stupid by jumping the gun. So, the problem: my phone has been randomly going into a boot loop. Problem can be replicated sometimes when I remove it from the charger. Occasionally it'll just restart itself and go into the loop. Thankfully a battery pull usually gets it back in business. This all started about two days ago.

At this point, I'd like to not necessarily return to stock, but instead retain root and run a clean, solid stock Sense (or AOSP) ROM with a solid kernel. However if it's recommend (or if I just should) return to stock, I'm fine with that. I should mention that I originally rooted with the "old school" method, way back when the Tbolt was new and had first been cracked open. After I rooted, I kinda did some rather noobish crap and flashed roms and kernels willy nilly, probably accepted OTAs--basically acted like a complete idiot. Here's some of my phone's info:

Android Version: 2.3.4
Sense Version: 2.1
Software Number: H3Y3BRIDTHEORY V1.0
Kernel: 2.6.35.13-nerozehl-dream-2.3.6-beta_SENSE+ nerozehl@Raehi #1
Baseband: 1.48.00.0930w_3, 0.01.78.0916w_3
Build: Hydra_1.0

As far as I know, I did not flash a different bootloader to the extent that the "old school" root method does/doesn't flash a different bootloader.

So that's the skinny. I managed to persuade Verizon to replace my phone (even though out of warranty, don't ask me how my semi-bogus story actually worked) and am expecting a RAZR MAXX any day now. I'd like to get my TBolt in good shape for my girlfriend to use as her phone is having issues and she's way out of warranty.

Thank you again for your patience and attention. Looking forward to your thoughts!