yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] c_live_lee:
Hey Jesse. I wanted to ask you, how long have you had your phone? You didn't happen to obtain s-off by using the Revolutionary method, did you? If so, that's your problem. You need to unroot in a different manner if you used Revolutionary. But it most definitely can be done.
[Thunderbolt Android Development] scotty1223:
what do you mean

'the device is still rooted" ? do you mean its still s-off? or it still has a working superuser in the firmware?

if youre still s-off,thats normal until you flash the hboot only file.

if youve still got superuser,then youve prolly still got all the rest of your data as well,and if you look at your firmware# youll find yourself to still be on the leak,and have not successfully flashed the whole RUU.

wrong image means that a properly named PG05IMG was found ahd checked,and contained an image that is updateable(if you changed "recovery" "clockwork" for example,it would find the file,check it,and not ask you to update),but when it tried to update,the file contained the wrong kind of image and coulndt flash it.

either your download is corrupt,or all the sd cards youve tried have been bad and/or need reformatted. did the md5 of your download match the one jcase listed?
[Thunderbolt Android Development] jessel0001:
As far as the phone it belongs to my wife, I rooted it shortly after launch using one of the original ADB Methods.

The biggest issue that I am having in this whole ordeal is that I am 1000 miles away from my wife and her phone.She has been having a myriad of issues with her phone. She blamed me and the rooting, and said she wanted it restored to stock. So I walked her through it step by step. Due to my distance I am unable to check first hand the MD5sum.

When I said still rooted, I meant that the phone still has a functioning superuser app. Not only that but CWR is still installed as well, everything else was wiped and the the stock OS appeared to be running. When I initially tried to flash the first RUU I had to use several SD Cards to get one to work. I even formatted them after the first unsuccessful attempts.

For now I think I will wait til I get home and do it first hand, in the mean time I had her install SHIFTS3NS3 1.3X, and so far no issues. (crosses fingers)

What would happen if she flashed a complete stock RUU?
[Thunderbolt Android Development] JBO1018:
If you are on one of the GB leaks I think you will get a main version older error and the flash will cancel. Though if its s-off I'm not really sure.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] scotty1223:
it depends on wich RUU you try and flash. you cant flash the mr1 becasue it will pop up a security warning and youll have to flash something newer to "unbrick" it. i *think* you can flsh an unmodified MR2 over custom firmware,but ive never done it,so if you want to try it,you can assume that risk. i seperated the hboot from mr2 so you can apply it exactly like this,and not have to OTA afterwards. flash the rom first,hboot second. you are welcome to use those files.

with an s-on,you can only go up. you cant backpeddle the firmware. with s-off,you can flash whatever the eff you want to ;) tho realize that the old 1.40.2000 eng hboot is not "permanent" and will happily overwrite itself with an s-on hboot.

from the sounds of it, she did not really apply the RUU. alot of folks think that the update is being applied when they see the status bars that appear when the phone is checking a file it finds named "PG05IMG". if it doesnt like the file,it wont ask to update. people see the status bars,then nothing,and think the update was applied.

is she wanting to return the phone to vzw? or just wanting to be stock becasue she thinks there will be no trouble?

if its the second option,might want to flash shadowmites hard patched hboot before flashing anything else. it will block hboot flashes,and remain s-off no matter what you do(flash ruus,OTA,run .exe files). its very handy- you can flash any ruu you want without worring about a security warning when youre trying to fix an issue,and since it will always stay s-off,its really easy to re-root if you ever want to root again. the only disadvantage is that it stays until you pruposefully remove it with some fastboot commands. easy to do if you rooted manually and have some knowledge of ADB,and have it set up and seeing your phone allready :)
[Thunderbolt Android Development] jessel0001:
Thank you guys for all your insight and help. I'm probably gonna end up perma unlocking the phone when I get home.
[Thunderbolt Android Development] enkrypt3d:
yea i figured that - my thunderbolt's power button wont work so i was hoping i could do it in recovery... no luck. but anyways i got it into the bootloader with adb and did it the long way. VZW is replacing my TB as we speak. Thx!
[Thunderbolt Android Development] scotty1223:
permanent s-off is here: http://xdaforums.com/showthread.php?t=1186022

let us know if you have further questions :)
[Thunderbolt Android Development] PilotML:
nm
[Thunderbolt Android Development] c_live_lee:
That isn't a typo is it? You seriously have S-on?
[Thunderbolt Android Development] c_live_lee:
Lol! Oh ok. Ignore me. I just woke up and so? Every things just aren't obvious to me yet, when they should be. I'll leave it at that. :) Anyway, don't worry. There is always a way out. I've never been in this situation, and am not nearly as knowledgeable as Scotty, but when he gets the chance, I'm sure he'll have you a good answer.
[Thunderbolt Android Development] scotty1223:
from the radio,and the 1.04.0000 hboot,you are on the 2.07.605.0 leak. you have 2 higher firmwares to flash to get rid of your security warning. and wont give you a "main version higher" error.

hang on a sec and ill find some links...

edit: i think i have misunderstood your question. are you stuck in hboot with a security warning or do you have a working phone? if you have a working phone with s-on,ill assume you have the stock recovery as well?
[Thunderbolt Android Development] c_live_lee:
I knew you would come to the rescue sooner or later! :)
[Thunderbolt Android Development] scotty1223:
so i guess you figured out your issue? :confused:
[Thunderbolt Android Development] adunski:
It seems like I'm having a similar problem, but I can't make any progress. first let me say that I've worked with a lot of different phones, and am very familiar with SDK.

So my TB boots straight into fastboot; with the exception of being able to boot into HBOOT. But trying to go into recovery just throws me back out to fastboot. I've tried to flash several RUUs now, but I get errors every time: usually 'main version is older'. I'm fairly certain I've seen 'main version is newer' trying to flash other RUUs.

I do have all of my drivers installed correctly. Previously I was able to use ADB and fastboot to access the phone. Now the phone won't interact with the pc, even when it shows 'fastboot usb'.

Normally I have the *** Security Warning *** at the top of my screen, but that goes away if I tell it to 'reboot bootloader'. I also reference S-ON at this point, but previously I was S-OFF. I was also previously rooted and happy with 2.2. Then Verizon wanted to push an OTA and I tired to go back to STOCK to see what that was all about. That's when I started having brick-like problems.

I've tried a lot of things, but coming up very empty handed. For reference:

MECHA XD SHIP S-ON

HBOOT-0.95.0000

MICROP-/

RADIO-1.02.00.0103_2r

eMMC-boot

Dec 16 2010,22:29:58

I really have gone through every tutorial I could find. Often it seems like people are seeing the same thing, but I'm always stuck not being able to flash the RUU I'm told will fix the problem.

Anyone been here before!?

EDIT:

Boo yah!

This version totally flashed for me:

PG05IMG_Mecha_VERIZON_WWE_1.66.605.2_Radio_1.39.00.0510w_NV_8k_1.41_9k_1.64_release_191132_signed.zip

I may have gotten it from here:

http://dougpiston.com/ThunderBolt/RUU/
[Thunderbolt Android Development] scotty1223:
sorry i didnt get to this earlier,i saw it but was on the road and unable to reply.

your .95 hboot is from the 1.03.605.10 firmware,there are at least half a dozen RUUs that could fix this for you.

"main version higher or newer " simply means that you cant flash older firmware over newer firmware with the s-on hboot,s-on will only let you go forward. 1.66.605.2 is the first mr2 leak,and is 1 version newer than mr1. flashing anything between those 2 should have also fixed it for you.

now that youre on newer firmware,you may want to go ahead and root via revolutionary,so that youll have a hard patched hboot and not run into this issue again. ;) from there you can flash recovery and superuser,and either flash a rom,or flash a newer ruu,depending on what your intentions are.
[Thunderbolt Android Development] Irieone:
I need to return a rooted Thunderbolt that I purchased in late June. I am quite sure it did not have MR1 when I received it.

If I flash the RUU + bootloader, will I get a prompt for the MR2 OTA? Do I need to accept and install before returning?

Call me paranoid, but I don't want to send a phone back with MR1 if MR2 was installed on my phone when I received it.

Can I just flash the RUU for MR2 + bootloader to bypass the need for an OTA update?

Thoughts?
[Thunderbolt Android Development] kesnik:
I purchased my T-Bolt on day 1 and rooted as soon as the community enabled me. I have been running non-GB bamf roms w/ the MR2 radios. I rooted using ADB.

I am looking to move to a different device soon and need to know the best (safest) way to return my phone back to a retail condition so I can sell it.

Is this the best way to go or is this an out dated method.

Thanks,

kesnik.
[Thunderbolt Android Development] scotty1223:
if you use this method,you will immediately OTA to mr2,so you wont have to send it in with mr1.

i would NOT reccomend flashing the mr2 in its entirety. depending on the firmware youre running,it may give you a ***security warning*** :eek:

the answer to both of you is that this method is still fine. after flashing mr1 with no hboot,flash the hboot,and then let the phone ota to mr2.

option 2 is to flash shipping firmware(1.12.605.6) in its entirety,as that WONT cause a security warning. again,youll immediately OTA to mr2. only advantage here is only 1 hboot flash.

if you want to unroot to mr2 without having to OTA,go this thread on android forums. i have mr2 files that are no hboot,and hboot only. you can use them with these directions.flash rom first,hboot second.

since you havent rooted with revolutionary,just scroll down to "getting current stock firmwar and s-on back on the phone" :)
[Thunderbolt Android Development] Irieone:
Thank-you!
[Thunderbolt Android Development] ErisKlown:
ok, I screwed up, I have done this time before and rerooted my phone. well i wanted to go back to stock, but when i went to install it i end up installing the wrong zip first locked my bootloader without installing the stock zip. Now my my bootloader is S-on and i cant do anything, Ive tried getting into recovery and it wont let me. Im not quiet sure where to go or how to get it Back to S-off since i cant access the phone through adb, any help would be great.

EDIT.........Got it Fixed and up and running from other threads that scotty posted in other fourms. I got irratated and did some research on other forums and found someone having a similar problem and i took a chance and it worked!!!
[Thunderbolt Android Development] sammyboy405:
So Ok heres what all I did.. I was having trouble with my radios. auto switching from 3g to 4g So I figured somehow or another I probably messed something up.

So I figured lets go back to stock.

So My bootloader shows

S-OFF (I didnt do step 2 of the OP Post)

HBOOT-1.04.2000

Radio 1.39.00.0627r

Feb 23, 2011

And Settings show

Baseband 1.39.00.0627r, 0.01.69.0625r

Kernel 2.6.32.21-g0606a3a

April 14th 2011

build 1.70.605.0 CL343953

Software

1.70.605.0

PRL 1.41_002, 1.64_002

PRL 15061

So by looking at those numbers.. Am I Pretty much Stock? Other than being S-OFF? Radios included?

And if I did need to goto S-ON i can just load the other part and get S-ON or no?

Also when Gingerbread OTA hits? How does this effect me? Or does it?
[Thunderbolt Android Development] scotty1223:
yes you are on mr2 with its matching radios,and an engineering bootloader.

idk if the 1.04.0000 hboot from mr1 is the same as the one from mr2,id need to compare md5s to make sure. unforunaTELY,i cant do that right now.

i *think* they are the same,but if you want to take no chances,or if someone wants to compaRE md5s,here is a 1.40.0000 from mr2: mr2 hboot only

from my unroot guide on AF

---------- Post added at 12:35 PM ---------- Previous post was at 12:34 PM ----------

glad you got it working. what did you do? just flash mr2?
[Thunderbolt Android Development] sprodigy:
Can someone let me know what the advantages to restoring S-ON for the bootloader are? I was thinking about leaving it unlocked, but will this prevent me from getting OTA updates?
[Thunderbolt Android Development] scotty1223:
There are absolutely no advantages to being s-on,in my opinion.

Leaving the 1.04.2000 eng s-off hboot will not prevent otas,but the gb ota will overwrite it with 1.05.0000.
[Thunderbolt Android Development] sprodigy:
Awesome, so I should be good with the first file flashed only?

BTW Scotty, I appreciate your recent initiative in this thread since it seems jcase has moved on!
[Thunderbolt Android Development] scotty1223:
you are quite welcome,glad i can help. :)

yes,you are good to go as you are. i do not believe there will be any issue with the GB OTA overewriting the 1.04.2000 hboot.

i also just verified that the mr2 and mr1 1.04.0000 hboots are 1 and the same,if anyone else needs that information. :)
[Thunderbolt Android Development] nemish13:
Using revolutionary to unlock wouldn't allow hboot to update

So anyone looking to get stock hboot back apply the fastboot change here and then it will apply:

http://androidforums.com/thunderbol...bolt-rooting-methods-updated-8-24-2011-a.html

---------- Post added at 10:48 PM ---------- Previous post was at 10:41 PM ----------

This leaves you with S-ON and MR1

Doing Software Update will download MR2 and then after reboot again will download the GB update (which will change hboot, so be sure you want to do this or wait for instructions here because you might not be able to root if you do this update)
[Thunderbolt Android Development] chip0:
So I'm a lol confused. I just got this phone on Craig's list.. it was already rooted. It's on 2.2 with some Rom how do I go back to stock? It says use same method as in root guide but I never rooted it so I'm not sure eat it means also in the root guide it says to put it these commands but it doesn't say how to get adb running....Wat do I do? I just wanna be stock again
[Thunderbolt Android Development] scotty1223:
go here

scroll down to "putting s-off and current firmware back on the phone" and download those files. follow the directions there. if you have questions,ask on that thread and we will help you :)
[Thunderbolt Android Development] jweaks:
Hmmm... not sure what's going on...

I have done this process before successfully, so I don't know what's wrong this time....

The first flash works just fine. The process completes and it's back to stock on reboot.

The second flash however is not taking... it says "bypassed" when I try to flash it.

When I reboot the bootloader is still the same and I still have "S-Off."

I re-downloaded the file and did Md5 checks. Everything is fine, but I still can't get the PG05IMG_hboot_1.4.0000 file to take.

Thoughts?
[Thunderbolt Android Development] scotty1223:
thats either your shadowmite or revolutionary permanent hard patched hboot. youll have to enter a couple commands in fastboot to remove it. directions here
[Thunderbolt Android Development] jweaks:
oh! I see. It was rooted with Revolutionary.

Thanks!
[Thunderbolt Android Development] MkVsTheWorld:
Does anyone know any guides for those people that rooted the manual way? I have to file a claim with Squaretrade (bad headphone jack).

In addition, I updated my LTE/CDMA radios. Not sure if I would need to downgrade the radios.
[Thunderbolt Android Development] scotty1223:
Same as the link above. Just skip the part about flashing the old Eng bootloader and skip to getting the newest firmware on the phone.

Alternatively,you can use this thread,and the allow your phone to OTA to mr2 after.
[Thunderbolt Android Development] CleveRuse:
Sorry, I'm confused too. ...so all I need to do is flash those two files from the OP seperately? I'm on a GB ROM (SynergyROM) with the 3.99 radio. Do I need to return to froyo first or not?

I need to return this device to Verizon.

Thnx

Edit: that doesn't make sense that is need to go to froyo first. I think the 4th post just confused me. I don't understand why he posted here. Guess he just wanted froyo back, not necessarily S-ON. Anyway, it confused me. Confirmation would be nice but ill prolly just follow the OP.
[Thunderbolt Android Development] CleveRuse:
....double post....
[Thunderbolt Android Development] scotty1223:
understand that the first post files will take you to mr1(1.13.605.7) wish is not the current firmware.

using the files here will create an extra step:

1)flash noboot RUU

2)flash hboot

3)OTA to mr2

if you go to the android forums link,there are are mr2 files that you flash in the same manner: ruu first,hboot second. using those files,youll be done and not have to OTA.

to everyone that is confused,please pay attention:

these files are a FULL RUU. they will replace everything that you have with the pieces from that firmware. everything will be replaced- your rom,radios,recovery,and hboot.

*it does not matter what rom/radio/etc/ that you are running. all of it will be replaced after flashing these files.

make sure you follow directions. flashing the hboot first WILL cause a security warning that will be fixable,but complicate your back to stock adventure.

once again,the files here take you back to the mr1 firmware.this method has not ever been undated to the mr2 update. using the files from the first post will create an extra step in the process(OTA-see above)

last and not least,if you have installed shadowmites permanent hboot,or rooted via revolutionary,you have an extra step-you must first replace the permanent hboot with the old,overwriteable eng 1.04.2000 hboot.

for those that cant go back to the previous page,the directions for returning to stock from permanent hboot are here on android forums

those who have rooted the old skool manual way can use these directions as well,just skip the first part about replacing the revolutionary/shadowmite hboot.
[Thunderbolt Android Development] ocbooger:
Just did this yesterday with no problems. Revolutionary wasn't available when I first rooted so it was as simple as flashing those 2 files in correct order.
[Thunderbolt Android Development] CleveRuse:
Ok, apparently I should have left more time for research ....but I didn't, so I need help.

I'm back to S-ON (least that's wut it says in my bootloader) and everything looks pretty stock-ish after flashing the first file ....but I've nvr had to flash from anywhere other than recovery or hboot.

Ho do I flash the second file? I deleted the first one, then moved the second (hboot) zip to my SD root, renamed it to PGO5IMG.zip then booted into the bootloader by pressing power+volume but obviously I don't know wut I'm doing cuz nothing happened ....and I'm rumming out of time, lol

Edit: Wow!!!!!!! LMAO! I confused the two devices,) Nvrmind. It worked perfectly! Thnx again for all the advice!
[Thunderbolt Android Development] dionysos803:
Does this with with stock GB TBs?

I've had to unroot my TB a number of times for a number of different reasons. Everytime I un-root my TB I come to this thread and I've actually used the non-rooted phones method, and I've never had any problems even when down grading from GB back to Froyo. It's always worked like a charm. I found the the correct way of going back to stock for rooted users lastnight and wanted to give it a try...I like it. I was suprised to see that the phone was able to get OTA updates again and of I wanted to compare the user experience I had from with a rooted GB ROM and the actual GB built HTC provides.

Now I'm bored with a stock phone again and wanted to re-root my phone. Will the non root user method work on a stock GB TB bringing it back to Froyo allowing me to root it the same way I've become familiar with?
[Thunderbolt Android Development] scotty1223:
No. The original exploits will not work with gingerbread. You could use zergRush to get a temp root and rewrite the misc image if you want to go back to froyo and root the manual way.

However,it would be easier to just root with revolutionary :)
[Thunderbolt Android Development] Ben's:
Figured it out, sorry for the meaningless post!
[Thunderbolt Android Development] leiko49:
clarification sought

Here are some questions about your directions, for my wish to return my thunderbolt to the orginal unrooted software.

1.	restore for root and non-root

a.	does “does restore for root” mean to restore to earlier software but keep the device rooted?

b.	Does “restore for non-root” mean to restore device to the original non rooted software?

2.	Assuming that restore for non-root is what I need to return to the original condition, unrooted

a.	Understand all directions except for the following: you directed us to download exploits.zip, but I am not sure what to do with it. While you say “next, push exploits.zip and misc.img, I see the directions for pushing misc.img, but no mention of what to do with the exploits.zip file, e.g., where to extract it.

Thanks
[Thunderbolt Android Development] scotty1223:
*this thread is outdated*

see this thread for current unroot procedures: http://xdaforums.com/showthread.php?t=1310014

why do you wish to return to stock,and how did you root?

if rooted "old school" thru adb: jump to the section entitled "Putting current stock firmware and s-on back onto the phone"

if rooted via revolutionary:

1)if you just want to be "unrooted" then jump to "Putting current stock firmware and s-on back onto the phone" and flash PG05IMG_2.11.605.5_no_hboot.zip

only

. you can flash the other file as well,but revolutionary will block it.

*id very strongly reccomend NOT messing with your bootloader if you just want to be "unrooted". there are no advantages to being s-on,and there are several to leaving the revolutionary hboot in place.

2)if you need to return the phone for a warranty claim,then you will need to follow the whole guide to become s-on.
[Thunderbolt Android Development] kesnik:
I picked up the Nexus and would like to return my Tbolt to stock. As I said, I used ADB to root and unlock the Tbolt initially.

I completed the steps listed here but I am not receiving OTA updates. It says the update service failed....

Any ideas?
[Thunderbolt Android Development] scotty1223:
this is an extremely outdated method. you may not recieve any OTAs with an inactive device. your best bet if you have restored the MR1 ota, is to downgrade the 2.11.605.5 ruu from the mecha shipped rom sticky thread and run it to get back to current firmware.
[Thunderbolt Android Development] kesnik:
Now that I flashed these 2 files I have no root and s-on. Do I have to root again? My goal is to return the phone to retail condition, I don't think its as easy as flashing the newest OTA. Is it? Thanks in advance.
[Thunderbolt Android Development] scotty1223:
no,you do not have to root again. you are on extremely OLD firmware now. there are several newer RUUs you can flash with your s-on hboot.

use this one,from footballs "mecha shipped roms" thread: http://www.filefactory.com/file/c0a..._NV_8K_1.41_9K_1.64_release_219938_signed.exe

note that this is an .exe file. you just need to download it,right click and run as administrator,if you have that optionl otherwise just run it. follow the onscreen directions.
[Thunderbolt Android Development] kesnik:
Thank you!!