yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] scotty1223:
You must not be using the command correctly. I have booted(without installing) a recovery on many HTC devices... including the inc 4g ;)

You must be unlocked,or running an eng or patched hboot.
[Thunderbolt Android Development] Ratbastrd:
I am unlocked, and running the "fastboot boot recovery recovery_signed.img" It says okay when completed. I then attempt to reboot unit and end up in the white HTC screen loop.

I am using the recovery from the .19 RUU

Am I doing something wrong?
[Thunderbolt Android Development] scotty1223:
You are not doing anything wrong,but its not working. Attempting to boot the stock recovery should boot you to the screen with triangle and !. You should not have to do anything else. Since the stock recovery is not starting,it may for some reason not be bootable(tho i have done it on other devices),or it could just be the fault of whatever is wrong with the phone.

You have tried this with custom recoveries,correct? There is prolly little to nothing you could do with the stock recovery.

The comment about not using the command correctly was directed at cyberkeeper,who is unable to get it working on his functional devices. Not saying anything bad,just that the command does work.
[Thunderbolt Android Development] Ratbastrd:
I think I have discovered the problem. The file that CK provided me, is "Thunderbolt_2.11.605.19_PG05IMG.zip"

I see this file as well RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed.exe

Which file do I want?

Which should I be attempting to flash from RUU mode?

Now that I am unlocked, which should I be attempting to boot images from etc.

Also, now that phone is unlocked, how do I lock again to attempt to flash the RUU file above from RUU mode or, alternatively load to directory and attempt to flash from hboot? If I relock, can I unlock again if needed.

This has gotten terribly confusing. My gut feeling is that the phone is not borked, but that I am missing the appropriate mix of files and process to complete the task.

thanks
[Thunderbolt Android Development] scotty1223:
aii yai yai. let me see if i can shed some light,lol

i feel the opposite. i think you have done a most outstanding job of trying to rescue the phone. you have tried literally every thing that there is to try. there are no other files or processes that could chnage anything.

i mentioned that you could try some different RUUs,but i do not believe that will have any affect.

i believe the phone to have emmc/hardware damage,wich is not going to be repairable via any kind of software flashing. i believe this based on the following:

-the ruu has run without error sveral times. the phone does not boot

-factory reset after ruu has been done. phone does not boot. (these first 2 things prolly fix 99.9% of fixable devices)

-you are unable to boota recovery,or install a recovery

-you are unable to get the OS running by booting the kernel

-your phone is still missing the main version,wich in itself is not a big deal,but having remained this way after severall ruu flashes is not normal.

hope that clears it up some :) if not,just holler what youre still confused about.
[Thunderbolt Android Development] Ratbastrd:
I give up, Tried everything again, including locking phone, loading image on SDcard and letting it flash that way. Went through entire process cleanly and rebooted to the white HTC screen, back into loop.

Tried RUU method, same results

Tried unlocking, flashing & booting both recovery as boot.img. Again same results.

I do notice that the radio has been updated, but still stuck in the HTC white screen loop.

I am done. CK, I may send you phone, if you want and can fix and send back to me great, if not understood.

Time to move on.

Thanks both of you for everything. I am going to keep me now working but previously waterlogged S3 as a backup.
[Thunderbolt Android Development] scotty1223:
You are quite welcome for the help. I wish we could have a different outcome. :( you definately get an A for effort. You've had incredible patience and persistance. :cool:
[Thunderbolt Android Development] santod040:
Good effort everyone, sorry to see it did not work out.

It does happen, the emmc can only handle so many writes and rewrites and some fail much sooner or later then others. :(
[Thunderbolt Android Development] rvnwlfdroid:
Lost 4g now I only have 1x

Followed everything and it all worked out with one exception. I now only have 1x for my connection. I used to have 4g. It's currently displaying

1.49.00.0406w_1, 0.01.79.0331w_1 for the Baseband version.

Thoughts?
[Thunderbolt Android Development] scotty1223:
that baseband is consistent for the ruu you just ran(2.11.605.19).

-first,make sure you have the back on the phone ;)

-second,try a factory reset from hboot
[Thunderbolt Android Development] cyberkeeper1:
you know if for some reason I never got this post. if you still have the phone and want me to send it to me I'd be happy to look at it.
[Thunderbolt Android Development] mdphoenix:
I have apparently thanked you too much today, or I would do so again. I'll be sure to come back tomorrow to thank this post as well.

Thank you again, Scotty. You have saved my ass and steered me in the right direction more times than I can count over the years.
[Thunderbolt Android Development] npro1464:
Hi all,

If there is ANYONE still on the Thunderbolt dev board, I'd be shocked. I'm looking to restore my old TB and take advantage of the $200 trade-in for a Note 4 promo. I bought the Thunderbolt and rooted it back when it was still on Froyo. I remember doing it through an adb method (much like the instructions posted on the OP). I really am looking to avoid doing that again. Would I be able to just flash the hboot files and be done with it?

Two questions:

1. I don't know what radio I'm on. Which one should/shouldn't I be on? Does it matter?

2. I'm on a Gingerbread ROM still, but I did flash to a ICS ROM for a little while and went back. Does that matter?

Don't mean to sound stupid, but I would like to do this right and avoid any headaches. Thanks!
[Thunderbolt Android Development] scotty1223:
i would recomend to follow the directions in the first post. this will make your phone 100% stock and OTAable to current ICS.

attempting to flash an s on hboot with mismatched radios or a non-stock rom could leave you in a bad,difficult(or impossible) to recover from situation.
[Thunderbolt Android Development] npro1464:
Thanks for the response! Cant believe there is still love on the Thunderbolt forum. Does the adp process work on Macs?

I'm going to trade my Thunderbolt into Best Buy for $200 towards a Note 4 [emoji41]
[Thunderbolt Android Development] scotty1223:
as long as you can set up adb on your mac,and get it working it should. sorry,ive not experience with that. i use either windows or ubuntu
[Thunderbolt Android Development] ushneb:
I'm feeling pretty stupid right about now. I followed the instructions in the first post but when it got time to flashing the first PG05IMG.zip, it wouldn't take. I got frustrated and downloaded an RUU thinking that would bring me back to stock. Well that didn't work and now I'm stuck with a black screen, HTC logo and 4 triangles with exclamation marks at the corners of the screen. I tried googling for a solution but have found none. Am I SOL? Any help would be appreciated.

Thanks
[Thunderbolt Android Development] scotty1223:
did you figure out your isue?

if not,we need results of

fastboot getvar all
[Thunderbolt Android Development] ushneb:
Nah, it's ok though. I was going to use the Thunderbolt as a trade-in but I was able to use another.

Thanks though.
[Thunderbolt Android Development] scotty1223:
have you ever flashed a radio? just like that. the phone must see the download exactly as "PG05IMG.zip". boot to hboot by power on/vol down from a powered off state. select yes when it asks to update. after its done reboot. yes,you can delete the file from your sd card with a file manager,or by connecting to your pc.

just flash a recovery in hboot,then flash superuser in recovery. just like the revolutionary method.
[Thunderbolt Android Development] choder:
worked perfect! Thanks
[Thunderbolt Android Development] aussiepunk:
+1 This worked perfectly for me thanks mate.

I had to make sure USB Debugging was turned on and that my phone was booted up in Charge Only mode for the adb to connect - I think that could get added to the instructions for the rest of the n00bs out there like me.
[Thunderbolt Android Development] rberry88:
Is there possibly a mirror for the nohboot file in the OP? It is an extremely slow download, shows 3% done after 30 minutes o.O
[Thunderbolt Android Development] a1exus:
mbp:~ alexus$ md5 hbooteng.nb0

MD5 (hbooteng.nb0) = 6991368ee2deaf182048a3ed9d3c0fcb

mbp:~ alexus$
[Thunderbolt Android Development] rberry88:
Do I just zip this file and name it PG051IMG.zip?
[Thunderbolt Android Development] a1exus:
sorry, i gave you wrong file... here go to this url you'll find all your files

HTC Thunderbolt 4G STOCK UNROOT S-ON | alexus's blog
[Thunderbolt Android Development] rberry88:
Awesome, thanks. Have to take my phone in to the store for warranty (case pulled away from side of screen).
[Thunderbolt Android Development] a1exus:
no problem... i've changed like 4 phones in the last few weeks, so i root and unroot htc thunderbolt on regular basis lately ;p
[Thunderbolt Android Development] rberry88:
Now does anyone have an idea how I can get back to before the version before the OTA so I can root again? I got a new phone from the store yesterday but they updated it with the new OTA and now revolutionary doesn't work to root.
[Thunderbolt Android Development] scotty1223:
you are stuck for the moment. i believe a new universal method is being worked on,wich hopefull will work here,and allow a downgrade.

as soon as i see something,i will post it.
[Thunderbolt Android Development] rberry88:
Didn't mean to hi-jack the thread, I was able to flash .5 again as a PG05IMG.zip and then root. Had to defer the OTA update as it tried to update as soon as the phone was booted again.
[Thunderbolt Android Development] scotty1223:
were you s-on when you did this?

just to make sure i understand your scenario:

-you otaed to 2.11.605.9 and were s-on

-you ran the 2.11.605.5 ruu and it worked

-you were able to root(yay!)
[Thunderbolt Android Development] rberry88:
Yep, I was unrooted with s-on (had to return phone to store for warranty and they gave me a new phone and before I realized it they had updated it with the new 2.11.605.9 OTA before I left the store). I put the 2.11.605.5 ruu on my SD Card as PG05IMG.zip and booted into the bootloader and let it update by itself (of downgrade in this case). After it was done I declined the OTA when the phone booted (hit defer after it downloads) and then used Revolutionary and rooted with s-off within 10 minutes. Happily flashing again :D
[Thunderbolt Android Development] Antny6:
From the original (non-revolutionary) root, wouldn't flashing the full 2.11.605.5 ruu (hboot and all) do the same thing?

Why would you have to flash the img with no hboot and then the hboot img?

I don't know...maybe I'm wrong (not an expert), I just don't see any reason the hboot needs to be flashed seperately...

EDIT: If you rooted manually (non-revolutionary), all you have to do is flash the full 2.11.605.5 OTA RUU. Completely removes root and S-off
[Thunderbolt Android Development] scotty1223:
it may be fine. or it may produce a security warning after the hboot is flashed and it realizes that the software on the phone is not factory(i.e. a custom rom)

i am 100% sure that flashing the hboot after flashing the matching firmware results in no errors.

you are welcome to flash a whole RUU that you want. there are other ways to skin the cat,but i post what i believe to be the safest and most reliable for the most people in the most different situations.
[Thunderbolt Android Development] halfcab123:
In additon in order to safeguard for some from getting a security warning it is a good idea to also do this:

adb push hboot-eng.nb0 /data/local

adb shell dd if=/data/local/hboot-eng.nb0 of=/dev/block/mmcblk0p18

adb push misc.img /data/local/

adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17

flash RUU zip from bootloader

and your done.

This will ensure there is no security warning based on versioning. Although

you may have not gotten a security warning it is possible that someone might.

The process of flashing the hboot-eng.nb0 from the system or from recovery will bypass the need for a password.
[Thunderbolt Android Development] scotty1223:
dont forget that youll need obtain said misc.img,and place it and the hboot into whatever directory you run adb from ;)

if anyone wants to do it this way,you could use the misc image from the original root. that way it will think you are running whatever ruu over a very old firmware :eek:

also...

updated OP with new files for 2.11.605.9 :)
[Thunderbolt Android Development] Chillerman:
Thanks for this thread. I wanted to share my experience. I received a replacement phone several weeks ago and rooted it via Revolutionary. I was having problems with the phone and flashed the 605.5 no_hboot file before calling a Verizon rep. She told me the 605.9 update should correct my problems so I did a search for updates and accepted the latest OTA.

In short, it did not remove my Revolutionary s-off. I then flashed Clockwork recovery in H-Boot and installed SU and viola! I am rooted with 605.9 and the new radios.
[Thunderbolt Android Development] CheeseMcGee:
Here's one for ya... I have to send back a phone that has a bad volume rocker - of course it is the volume up button that is broken!

I have S-OFF, but I have no way of installing the PG05IMG files. Help!
[Thunderbolt Android Development] scotty1223:
you can run the PG05IMG in fastboot. i spose i should migrate these directions over here as well: http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272416

i originally came up with these directions for someone who had no screen,hence the extreme amount of checking for connectivity(fastboot devices,adb devices :eek:) but it should work just fine for no volume rocker,its all done thru fastboot on your PC :)
[Thunderbolt Android Development] CheeseMcGee:
You are the man!!! Took me about 10 minutes and now I can send it back without fretting. Thanks a ton. :D
[Thunderbolt Android Development] Trigster:
Question, I just got my replacement TB.

And apparently in the dropping the USB no longer works with the mic. Is there anyway to lock the boot-loader backup to stock w/o usb? I would really hate to just flash the stock OTA over the phone, only to have tech load the boot-loader only to find its unlocked yet. :(
[Thunderbolt Android Development] technomaje:
Quick question. My wife's Thunderbolt has gotten to the point where it will only run about three minutes until the OTA tries to install. I kept defering and now it won't give me the option anymore. Reboots and goes to a black screen with the Blue Android.

So I guess I've got to unroot the phone and allow the OTA to take. Are the directions below where I should start?

I've got a T-Bolt running Thunderstick, and it's off OTA for the moment. Both were rooted with Revolutionary. I'm going to relock mine since I"ll be selling it. Got me a Droid Bionic.

[/CODE]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)PG05IMG_no_hboot_2.11.605.9.zip

md5: 3e189b6c85ea7da1e26e12a5cd7b1ab0

2)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

. again,please post any questions before doing anything.

last and not least: if you have non working hard buttons,or no screen,see the directions in this thread on AF[/QUOTE]
[Thunderbolt Android Development] scotty1223:
You don't need to unroot just to accept an ota. Just install the stock recovery,accept the ota,then reinstall whatever recovery you're currently running and reflash super user to reroot.

download the stock recovery from here http://androidforums.com/thunderbol...dios-recoveries-hboot-updated-12-18-11-a.html

Flash it in hboot like any other recovery or radio
[Thunderbolt Android Development] technomaje:
I'm running CWM, whatever version was in Revoluationary.

Thanks for the tip. She'll be happy to have her T-Bolt back again.

EDIT--- Wasn't sure which one to do, so I did the next to last one, since this is an OTA update. Once it was flashed and rebooted it stayed on for about 30 seconds before it went down to install the OTA. Didn't have a chance to delete the file from the card, so I pulled the battery and the SD card. It's rebooting now, and should immediately go down for the OTA install. Let you know what it looks like on the other side.

EDIT 2 --- Worked like a charm. Thanks. She won't let me get it back from her so that I can get root access back. I only had it rooted so she could tether her Xoom to it. I'll steal it back in a little while and get root back.

Thanks for the help, I really appreciate it. Was a lot easier than I thought it was going to be.
[Thunderbolt Android Development] scotty1223:
no prollem. thats one of the many advantages of revolutionarys permanent patched hboots.

most folks freak out about OTAs and make them into a much bigger deal than they need to be ;)

one last thing, consider leaving the revolutionary s-off on the TB you sell. just flash the "no hboot" file to make it stock again.

as youve seen, the recolutionary hboot does not affect a stock phones ability to recieve OTAs,or do any other thing that stock phones do. further,it offers many advantages over a stock s-on hboot by having extended range of available fastboot commands,and the ability to flash ANY RUU,not just the one its on or higher. both could be very handy if the phone is soft bricked. not to mention if a buyer of the phone down the road wants to root,it will be easy :D

after flashing the no hboot file,it will be stock. someone who buys the phone with intention to leave it stock will never know revolutioanry s-off there,and someone with some knowledge of rooting that buys it will prolly be pleasantly surprised ;)

just my 2 cents. ive sold lots of rooted and s-offed stock phones,and the rooted part always seems to generate a lil more interest. not sure why people think they need to return a phone to stock to sell it.
[Thunderbolt Android Development] jeremydallas:
Latest OTA "SERVER UNAVAILABLE"

All,

I have searched for a solution to this and sincerely apologize if it is posted somewhere in here and I either didn't see it or didn't follow directions properly.

I used revolutionary a few months ago and it is/was awesome, but when the latest OTA pushed to my phone around December 21st I woke up to find a yellow triangle with an android guy and my phone wouldn't boot. After doing some searching I followed directions to download what I thought was a stock recovery image and reset my phone, which got me back up and running (I'm on Android 2.3.4, Software 2.11.605.5, PRL 15088).

However, now every single morning I wake up to find a "SERVER UNAVAILABLE" pop-up to which I click OK. Whenever I do a software update check it tells me there is a 36.125MB package available, but when it tries to download it gives the same error message.

FYI - Whenever I boot to recovery I have the following txt:

-Revolutionary-

MECHA XD SHIP S-OFF

HBOOT-6.04.1002

MICROP-/

RADIO-1.48.00.0906w_1

eMMC-boot

Feb 23 2011, 20:42:55

HBOOT

etc...
[Thunderbolt Android Development] scotty1223:
if youre running a stock recovery now,you may need to do a factory data reset,or reinstall a custom recovery long enuff to wipe cache.

then the OTA may re download and apply.

alternatively,just flash a rooted stock 2.11.605.9 rom,or a cstom rom based on it,and be done. you can prolly flash it over what you have without a data wipe and not even lose your data.
[Thunderbolt Android Development] DroidHam:
im having trouble getting ADB to see my device, all my computer sees in the SD card, ive tried toggling the usb debug on and off with no success. Any ideas? Im using MIUI

---------- Post added at 09:48 AM ---------- Previous post was at 09:43 AM ----------

im not worried about unrooting, i just want to get it back to stock since i sold it on ebay, can i just download the 2 files, reboot to fastboot from my ROM And flash them?
[Thunderbolt Android Development] thebigthn:
I cannot get my usb port to work for the life of me. I did all the troubleshooting I could, but is there a way to do all this without connecting to a computer? I tried a program called ADB wireless, but my serial number doesn't show up in step #8.
[Thunderbolt Android Development] scotty1223:
did you root via revolutionary? or old school?

you can get back to factory firmware without the usb port,and if you rooted the old way and have the 1.04.2000 eng hboot allready,you dont need the usb port,just move the files to the sd card with a card reader 1 at a time.

there is no way that i know of to get rid of the permanent hboot at this time without fastboot.

there was supposedly a "return to stock" app in the market,but i have no personal experience with it,so try at your own risk :eek:
[Thunderbolt Android Development] tangsta35:
I dropped my phone in a puddle, and the volume up button no longer works. The good thing is, Verizon has agreed to replace my phone, and now I need to ship the old phone back. So I've read the guide on how to unroot, and watched a few youtube videos. Every video I saw seems to require the "volume up" button to confirm the final flashing process in hboot.

I did a quick search and according to this thread, im screwed:

http://xdaforums.com/showthread.php?t=1440952&highlight=broken+volume

Does anyone know if its possible to re-map or bind one of the soft keys to this volume up button instead?
[Thunderbolt Android Development] scotty1223:
you are far from screwed. no usb,maybe youy are screwed :eek: ,but no screen or buttons you are fine.

just use directions in 5th post here: http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
[Thunderbolt Android Development] scotty1223:
check out this post: http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272198

let me know if it works. just be careful and make sure the md5s match where it says they must :)
[Thunderbolt Android Development] PieceKeepr:
I need to return my phone to VZW for warranty replacement but I'm having trouble getting back to stock. I had trouble downloading from the links in this OP so I used the ones in the original thread here. The rom flash worked but I cannot get the bootloader to go back to the stock s-on loader.

I have verified the md5's and reflashed a few times but not getting anywhere. Any ideas? And also, I rooted with Revolutionary.

Edit: Got it figured out. Now if I could get the GPS to work ...