yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] scotty1223:
sure,no prollem at all :)

heres the link to our "how to" thread: http://androidforums.com/thunderbolt-all-things-root/353591-how-some-root-terminology.html

this should hopefully take you to the remove perm s-off post: http://androidforums.com/thunderbol...91-how-some-root-terminology.html#post3061599

feel free to repost,or link to it :) glad to see other folks lookin our for their fellow forum members :cool:
[Thunderbolt Android Development] shovelheadhd:
After the new gingerbread release I finally see the value of having this type of hboot. I originally wasn't planning to update my hboot but after considering trying the new leaked official gb ruu and seeing ppl ending up with s-on it hit me that this is why I needed this hboot.

Generally I don't accept ota updates but just like most others I love flashing roms and trying out updates and such. So no I have a bit of piece of mind about new ruu's and not worrying about ota updates as much kind of like when I had my og droid.

So my thanks go to the devs that created this and the op for posting this!
[Thunderbolt Android Development] scotty1223:
i am the same way. yesterday i flashed the leaked,untouched RUU. this preserved my s-off,so i then simply flashed twrp in hboot and then flashed the "working superuser for TB sense" in recovery.

im now running a rooted official GB build :)

when the official OTA starts pushing to phones,ill go back to mr2,install a stock recovery and let myself OTA to it. neither of these things would be possible without this :cool:
[Thunderbolt Android Development] scotty1223:
yesterday i confirmed you can overwrite the revolutionary hboot with fastboot,i changed back to the original eng 1.04.2000.

i also flashed the leaked 1.05.0000 hboot and confirmed revolutionary works with that. ran the tool again and im back to permanent s-off :)

heres what the bootloader will look like on a stock phone that accepts the GB OTA,if anyones curious :eek:

the pink LOCKED is because it has htc unlock support included
[Thunderbolt Android Development] Veridor:
Any reason to update to that leaked HBOOT?
[Thunderbolt Android Development] scotty1223:
no! unless you want to be s-on,for some reason. i just did it because i have too much curiosity ;) i wanted to verify revolutionary would root it. it worked fine,but i still wouldnt reccmend that people mess with their bootloader unneccessarily,its too risky.

if you had this,youd need to run revolutionary to become s-off again,or wait for htc to provide a key. :eek:
[Thunderbolt Android Development] Brokn:
I've updated to the leaked RUU, now i want to get root, im trying to use the fastboot command on first post to flash the hboot and im getting

>fastboot flash hboot hboot_7630_1.04.0000_110223.nb0

sending 'hboot' (1024 KB)...

OKAY [ 0.172s]

writing 'hboot'...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 0.297s

how do i fix this prob?
[Thunderbolt Android Development] scotty1223:
Wat hboot do you have? I'm not sure I understand what you're trying to do. If you're s-on all you need to do is use the revolutionary tool. If you're s-off,you just need to flash a recovery,then superuser.
[Thunderbolt Android Development] Brokn:
Im on s-on, on the latest gingerbread leak, unrooted. Trying to root this TB. So you recommend using revolutionary tool?
[Thunderbolt Android Development] scotty1223:
Yes. It works fine with 1.05.0000 :)
[Thunderbolt Android Development] thepolishguy:
Scotty- I sent you a pm so I wouldn't derail this patched hboot thread. Thanks for any help.

Shadowmite- I flashed this yesterday. Thanks so much for your help. Is the Revolutionary method this same patched hboot (just for knowledge sake?).
[Thunderbolt Android Development] marcogiudice:
what a spectacular freaking write up, wow! that deserves to be on every thunderbolt forum and stickyed.. very impressed! thank you
[Thunderbolt Android Development] scotty1223:
reply sent. i plan to run the RUU later,for sh*ts and giggles :p

yes,they are the same... he said this back on page 5 or 6:
[Thunderbolt Android Development] scotty1223:
sorry i didnt really answer this,earlier,i was driving :eek:

to answer it now,to fix the prollem you need to be s-off. an s-on bootloader has very limited flashing capabilities,and a much smaller list of available commands. the reason your siginiture check failed was becasue you were attempting to flash something not approved and signed by htc.

were you able to run the revolutionary tool and obtain s-off/root?
[Thunderbolt Android Development] vinylfreak89:
the command posted on the first page will work on the revolutionary tool as well to unlock hboot writing. then flash hboot in fastboot to unroot after you flash an unroot RUU. note that it will STILL be locked via RUU flashing until u flash over an S-ON hboot
[Thunderbolt Android Development] scotty1223:
confirmed working when flashing an RUU(not that i doubted :D)

updated to latest leaked ruu and still s-off. :)
[Thunderbolt Android Development] marcogiudice:
where di you find the leaked 1.50 hboot? id like to have for my files
[Thunderbolt Android Development] scotty1223:
jcase leeaked it on twitter,or on rootzwiki... i forget wich. you can download it here: http://www.multiupload.com/20KTIP03NH

you can pull the image out of the inner PG05IMG,or keep the PG05IMG,however you keep them filed :)
[Thunderbolt Android Development] jmc2543:
So being that this modifies/replaces the hboot is there a way to get back to the unmatched hboot?
[Thunderbolt Android Development] thepolishguy:
If I understand you correctly -yes- I believe it is right here in the op...

I think that is what you were talking about?
[Thunderbolt Android Development] scotty1223:
pssst! *tapping shoulder* check out post 44 on page 5 for some more detailed info of what was listed in the original post. :rolleyes:

it works,ive done it. it works for this 1.04.0000 patched hboot,and for the 6.04.1002 version that comes in the revolutionary root tool.you are not by any means "stuck" with one of these hboots if you need to return to 100% stock for a warrantly claim.

heck,you might learn some other stuff if you read the rest of the thread :D
[Thunderbolt Android Development] jasonpantuliano:
Might be a stupid question but I just lost data on my bolt so they are sending Me a new one tomorrow. I'm down the beach with no computer access. Just my tablet and phone. Will I be able to flash this over am s on bootloader so I can flash a rooted ruu.
[Thunderbolt Android Development] jasonpantuliano:
Also I know I can get data back if I can get s on but can't do that without a computer either due to the fact that I flashed this boot and can't flash a new one without fastboot commands. I knew I should have put Ubuntu on my tablet before I left for the shore
[Thunderbolt Android Development] scotty1223:
no. you have to flash it over an s-off bootloader.

what are you talking about? i thot you were allready s-on per the above post? :confused:

being s-on or s-off has nothing to do with any kind of data signals anyway.

download an lte on/off app,and set it to "cdma only" or "cdma w/o EvDo" and tell me if you can then get 1x. not cdma auto,not cdma/LTE auto, set it for a cdma only signal. give it a few minutes for the 1x to pop up.
[Thunderbolt Android Development] jasonpantuliano:
Ur wrong the only way I can get data is to flash a sense based rom and go to ##778 and modem settings and set my rev a to enabled. But when I switch back to erhpd or whatever I lose data. Can't get 4 g without the ehrpd thing. So they are sending Me a new phone to my shore house. My 4th one because of this. So what I'm asking is when I get my new phone tomorrow will an s on hboot allow Me to flash this and unlock the bootloader. I don't have a computer at my shore house. Justin my Acer tablet
[Thunderbolt Android Development] jasonpantuliano:
Not trying to sound like a **** but I'm far from a noob have tried everything. Search thr forums this has happened to many people and the only way to fix it is to get back to s on on a stock rom but I can't casue I flashed this hbooy and have no computer to flash the fastboot commands. They are sending me new phone.
[Thunderbolt Android Development] scotty1223:
as i said above,no,you cannot flash this over an s-on bootloader.

going to a sense rom and dialing ##778 still has nothing to do with being s-on or off. you can do that with an stock hboot,or this one,or with the original 1.04.2000 eng hboot,it doesnt matter. ive experienced data loss as well,but since im wrong, i wont say anything more about it.

sorry,but youre going to have to get back to a computer and re-manually root,or run revolutionary to reroot your phone.
[Thunderbolt Android Development] scotty1223:
im not trying to be a **** either,but your choppy sentences and typos from typing on your phone,tablet,or whatever, dont give enuff information for people to tell what youre talking about,and certainly make you sound like a noob.

im on the forums plenty,and ive never seen anyone have to go back to s-on to get data back.

if flashing a stock rom works for you then find a wifi spot,download the mr2 RUU,rename it PG05IMG and flash it. fix your data,reinstall your recovery via your permanent patched hboot and either flash superuser to root the rom youre on,or just flash one of your backups.
[Thunderbolt Android Development] jasonpantuliano:
Tried that and none works. Still can only get data using the rev a enabled method. No 4g that way though. Thanks for your help. I need a computer. About to go to a library tomorrow
[Thunderbolt Android Development] JBO1018:
To me "the only way I can get data is to flash a sense ROM." makes it sound like perhaps you are not running the right radio for the ROM your wanting to use.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] jasonpantuliano:
No I flashed a stock mr2 ruu and still a no go. I've been through 3 phones because of this. The one thing that has worked was going back to s on and I'm on vacation with no computer/adb access
[Thunderbolt Android Development] scotty1223:
sorry we cant be of more help. you are the first person i have ever encountered that claimed they had to go back to an s-on hboot to get data. good luck.
[Thunderbolt Android Development] jasonpantuliano:
Thanks for your help anyway. If u search on Google you will see a few other people have had the same problem as me and s on worked. Before I received my last replacement I put the phone back to s on after trying all the things that u mentioned and it magically worked again. Doesn't make any sense to me either.
[Thunderbolt Android Development] Geekbabe:
I used the revolutionary tool to flash, my HB version is listed as 6.0.4 1002 do I need to flash this new patch?
[Thunderbolt Android Development] scotty1223:
Even if it would let you,there's no reason to. Other than the version number,they are the same :)
[Thunderbolt Android Development] Geekbabe:
lol, thank you, I'm functioning in idiot mose this morning I think
[Thunderbolt Android Development] jasonpantuliano:
Hey Scotty just thought u may like to know. After I received my new phone from fed ex today and put in my sim I still had no data. II decided to go buy a sim card and put it in the new phone still no data. I put the new sim in old phone and everything works great. So turns out it was just a bad sim. Thank u for ur help by the way. I appreciate it
[Thunderbolt Android Development] scotty1223:
thanks for posting the fix,glad you got it working :)
[Thunderbolt Android Development] jmc2543:
Thanks for the info guys. Went and reread ALL posts and found answers that I would of gotten if I had done that to begin with.
[Thunderbolt Android Development] maddog241:
Please forgive me in my current knowledge-limited state (politically correct for NOOB), but I am trying to learn.

I came from BB as many have, and there you just flashed whatever suited your fancy on any given day, or reverted back if something didn't go so well. Now I find I can't do that quite so easily with Android. After reading this thread, it appeared to me to contain the ability to unlock the bootloader so that would be possible, but do I understand correctly that this cannot be flashed over a stock bootloader? That you already have to have s-off in order to flash this patched bootloader for permanent s-off?

I always liked testing leaked roms, and I would really like to have that state for flashing or reverting as needed, but I'm not clear on how to get there. Can someone please help me understand this?
[Thunderbolt Android Development] scotty1223:
\

that is correct. you must flash this over an s-off bootloader,not a stock-s-on. at the point,this hboot will protect itself from being over written. if youve looked at the rest of the thread,youve seen my pics and comments. ive flashed ruus in hboot,ran .exe ruu files, and even accepted OTAs and this hboot always remains. it will stay until you remove it purposefully,wich is possible in case you ever need to return the phone to 100% stock for a warranty claim.

sounds like this would be perfect for you. you can flash new leaks in hboot,run .exe files or whatever you want,and this will remain so no matter what you do,root is ALWAYS a couple of flashes away.

i assume you are not rooted now?

if you are... just download,remove the inner PG05IMG file and place on your sd card.check the md5 on your phone against that in the included "read me" text file,and then flash in hboot.

if you are not rooted,just use the revolutionary tool to root. it will give you this same permanent bootloader,and install clockwork recovery. you then just flash a superuser in clockwork recovery and you are rooted,and all your current data is preserved.

for more info,and download the revolutionary tool/ superuser see:

http://revolutionary.io/

hope that helps :)
[Thunderbolt Android Development] firestorm126:
Just to confirm... is this still the most recent hboot for the thunderbolt? I've seen somethings about 1.05 going around.
[Thunderbolt Android Development] scotty1223:
yes. this is the most recent hard patched hboot.

1.05.0000 is the hboot for the upcoming GB OTA. it contains htc unlock support,but is an s-on hboot.
[Thunderbolt Android Development] boblpn:
?

From reading this, I understand that this is a very good idea, but, as a new Android user, I am a bit confused.

I have already rooted my TB, and have the current stock VZW ROM, debloated it, and have TiB, CWM, Root Explorer, etc installed.

If I understand, this is for protection of accepting OTA from VZW?

What if I want to flash customs, or other ROMs in the future? Can they still be flashed from HBOOT as normal?

Please explain.

Thanks.
[Thunderbolt Android Development] scotty1223:
the biggest thing this does is protect you bootloader from accidentally becoming overwritten with an s-on bootloader. i suggest reading the posts carefully from page 1,and it should be come fairly obvious the advantages.

it protects from ota in a sense... if you are on a stock rom/recovery with this,it will remain after accepting an ota. if you are rooted and running a custom recovery(clockwork or TWRP) then the same rules apply DO NOT ACCEPT AN OTA.

yes,it flashes everything the same. think of it this way: it does everything that your current eng s-off bootloader does,but is permanent-cannot be removed unless you do it purposefully with the fastboot commands on page 1. the 1.04.2000 eng s-off will happily overwrite itself with an s-on hboot if you apply an OTA or RUU.

hope that helps,i cannot think of a way to make it any clearer. again,id highly reccomend to read thru the thread,lots of info to help clarify it for you. :)
[Thunderbolt Android Development] sidsixseven:
You won't lose S-ON from the OTA, but you may have to reflash Superuser. In my opinion, if you are already rooted and smart enough to not accidentally flash an S-ON bootloader, this is not necessary to flash. Although, won't hurt either, just a little more difficult to return to stock.

Sent courtesy of SID 6.7 and Tapatalk
[Thunderbolt Android Development] scotty1223:
this bolded part is the key. im not saying that the wave of first time smartphone/android/root users are stupid,but ive seen quite a few folks flash ruus not realizing it would remove the s-off and root. either becasue they thot it was a radio file,or they just thot it was rooted and they could try it out. :eek:

also quite handy if you find your self stuck at a splasn screen or in a bootloop and recovery flashes arent fixing it. if you need to flash an ruu to try and fix an issue,or return to a stock rom for a verizon visit,having this makes it really easy to re-root.

the removal commands are easy,if you need to change it. especially if you rooted manually and thus have adb set up and a lil experience with it.

while i do agree its not a neccessity,IMO its benefits are enuff that its something i highly reccomend people flash. just my 2 cents. :)
[Thunderbolt Android Development] sidsixseven:
Agreed. If you don't understand what you are flashing before you flash it, then this is definitely a safer bootloader. To me, that's common sense but people get flash happy and don't always read or understand what they read.

Foe example, I'm seeing a lot of people flashing the new RUU with the new **locked** bootloader. Only way to re-root from that is Revolutionary. Thankfully, that puts this bootloader on it so they can't make the same mistake.

Sent courtesy of SID 6.7 and Tapatalk
[Thunderbolt Android Development] JBO1018:
I think some of it could be from people who had previous phones that were actual Radio s-off. (@secuflag actually turned off in the radio firmware.) That makes it just as safe as this patched hboot I believe. So it might not have occured to them we don't really have true s-off, just an s-off ENG hboot.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] scotty1223:
yes thats very true- if you came from an incredible especially youd feel like you could do whatever you wanted. there was no eng bootloader,so it didnt really matter what hboot you used. you just used what was newest,and changed it at will,and always remained s-off.

radio s-off would be better IMO,but this is basically producing the same affect. you needed to run unrevokeds s-on tool to turn the radio back to s-on. im sure a similar tool will be released by revolutionary to put back a stock hboot.

again,im not criticizing... its easy to understand how/why folks have accidentally dont it.this will prevent alot of future mishaps :)
[Thunderbolt Android Development] taikyosan:
THANKS!

I had flashed a S-On leaked RUU after returning to stock. Camera went wonky and i need to do revolutionary to apply fix. Then i manually tried to update market (and broke it lol.) So i needed to reflash the RUU but wasnt sure if it would work (even after reading from beginning to this point.)

So i took a leap of faith and flashed the latest leaked RUU from the official TB rom listing sticky thread. After that i received an OTA, and that went through. Checked to see if i was still S-off and i was! Market works and is updated! I was finally calm enough to eat lunch lol.

Of course Clockwork recovery is gone (red triangle with exclimation, is that the security warning?) but i can reflash that with with the revolutionary way of rooting correct? or do i even need it since i am currently content in waiting for the GB RUU.
[Thunderbolt Android Development] scotty1223:
if you really want the GB OTA update,youll need to either:

1)not install clockwork and stay stock.

or

2)install clockwork so you can root,but reinstall the stock recovery when the OTA starts being pushed to phones.

if you wish to root and be rooted until the OTA arrives,do option 2. the OTA will take root away when it flashes,but you can easily reroot after its done by reflashing a custom recovery,then flashing superuser from that recovery. you can get the stock recovery from here.

the OTA does not care about rooted firmware. it does care about clockwork recovcery. trying to install an OTA with clockwork results in a potentially unrecoverable bootloop,so dont do that.

the red triangle an ! you are seeing are the inaccessible stock recovery.
[Thunderbolt Android Development] taikyosan:
So that means that I am set for the gb update.
[Thunderbolt Android Development] scotty1223:
that is correct. :)
[Thunderbolt Android Development] taikyosan:
Im trying to revert my phone back to stock boot loader. When i tried the commands on the first post it said fastboot: permission denied. Do i need to root the phone first?

I am using the drivers found http://unrevoked....hboot_driver_install

I guess that might be a dumb question. I'll try rooting it first but fill free to answer though if want lol.
[Thunderbolt Android Development] taikyosan:
Tried again and this is what i get:

E:\android-sdk-windows\platform-tools>adb shell fastboot oem mw 8d08ac54 1 31302e30

fastboot: permission denied

I did root, tested it with root explorer. What am i doing wrong?

(edit)

When i try doing it from within shell i get:

E:\android-sdk-windows\platform-tools>adb shell

$ oem mw 8d08ac54 1 31302e30

oem mw 8d08ac54 1 31302e30

oem: permission denied
[Thunderbolt Android Development] scotty1223:
Why do you want the stock hboot back? I'd reccomend to stay with he revolutionary s-off unless you need to send it in for warranty.
[Thunderbolt Android Development] taikyosan:
I need it for warranty, my screen is getting worse (i got the phone used lol :/)

---edit---

I totally like revolutionary and definitely plan to reapply on my replacement.
[Thunderbolt Android Development] scotty1223:
You are able to warranty a used phone?:confused:

At any rate,you'll need to be in fastboot,not hboot,and not in the OS in charge mode. I'd highly reccomend flashing the old Eng 1.04.2000 hboot first,wich you can overwrite afterward.

Be very careful. Fastboot will NOT do any security checks and will flash litterally anything you tell it to for a bootloader. Get it wrong,and the phone is a an unfixable paperweight.

I've got a remove revolutionary hboot and return to stock guide here:

http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html

Hopefully it will help :)

Let us know if there are other questions.
[Thunderbolt Android Development] taikyosan:
Yeah its possible, i have full coverage, that includes at faults accidents (like water damage.) You still pay the charge for the replacement but its replaceable.

Also thanks! I'll give it a go. I would rather use my thunderbolt for as long as possible (or until a phone i wan't comes out lol.) I'll post how it goes.
[Thunderbolt Android Development] taikyosan:
It was a success.
[Thunderbolt Android Development] marcogiudice:
Damn that Scotty85 is a nice guy!
[Thunderbolt Android Development] mbaby2672006:
Is there a way to undue the patch without dab because for some reason my TB has stopped connecting with my computer and have to send it in for warranty if I can't fix it.. PLEASE HELP ASAP
[Thunderbolt Android Development] scotty1223:
http://xdaforums.com/showthread.php?t=1310014

follow directions to remove revolutionary hboot
[Epic 4G Q&A, Help & Troubleshooting] crawrj:
OK so a couple of people posted in my thread that 3G was horrible on EG22. I had read reports that it was improved on EG22 and had not noticed any issues yesterday or this morning. So I jumped off wifi and began trying to download speedtest so I could check my speeds. I can't even get anything to download from the market. I tried HBOGO, which I used this morning, and it won't run. Tried netflix and it won't even connect. So I wanted to find out if this was a network issue or modem issue. Please let me know how your 3G is working right now and if it is working good what modem and area. I am in Louisville KY.

Edit: I was finally able to download speedtest. I am getting 900+ pings, 40ish kbps down and 85kbps up.
[Epic 4G Q&A, Help & Troubleshooting] crawrj:
OK it just came back to life. Hope it was just a network issue.
[Epic 4G Q&A, Help & Troubleshooting] JohnCorleone:
I had my network drop out temporarily earlier today and I am nowhere near you. Made me nervous for a second..