yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Ratbastrd:
C:\tbolt>fastboot erase cache

erasing 'cache'... OKAY [ 0.203s]

finished. total time: 0.203s

C:\tbolt>fastboot flash recovery recovery.img

sending 'recovery' (4872 KB)... OKAY [ 0.796s]

writing 'recovery'... INFOsignature checking...

FAILED (remote: signature verify fail)

finished. total time: 1.608s
[Thunderbolt Android Development] scotty1223:
Oh... Best way to get pg05img off the SD is a card reader. In a worse case,you can prolly have a store put your battery in a phone and charge it.

Or just get an external charger. I got one on amazon with a couple batteries fr somewhere around $20
[Thunderbolt Android Development] scotty1223:
uh oh. mdm9k is the lte radio. radio or hboot flash failing for any reason(unplug,battery dies,etc) is never good and may not be repairable. your only chance is to wait for a charged battery and try and run the ruu again. keep your fingers crossed,as its pretty likely the phone is now irrepairably borked. :(

it is also possible that the flash failed becasue the radio was allready damaged,and didnt fail becasue the phone died.

the screen youre in is the "ruu failed" screen for lack of something better to call it.

you can try the folloeing to get you back to normal fastboot:

fastboot oem resetRUUflag

fastboot reboot-bootloader

of course,the resetRUUflag command may no longer be available since your "eng s on" hboot has been overwritten with 1.05 :(

failing the above,you will have to flash something to get out of ruu mode. now that youre normal s-on,that will have to be a signed file. :(
[Thunderbolt Android Development] scotty1223:
hope that cleared it up some :)
[Thunderbolt Android Development] cyberkeeper1:
have you tried to reboot manually into hboot after a battery pull? (power+vol down) does it directly go to RUU every time you power it on? also, what is the difference (if any) when powering up manually versus just plugging in the cable from power off mode and letting it come up on its own? (because there is no recovery it will do this)
[Thunderbolt Android Development] scotty1223:
im not sure what youre asking here. at this point,youre not able to install a custom recovery to flash a rom with. you are s on,and prolly now on a normal ship hboot. unless you can find twrp,cw,etc,in a file signed by htc,youre SOL ;)

you cannot use the stock recovery to install roms,and even if you could,you cant install it,other than in the ruu,unless you could find it in a "singed by htc" file. you in fact have the stock recovery on the phone now,after running the ruu. (im assuming you mean "stock" when you say "original")

if you havent borked the LTE radio when the phone died,you are lucky,and id pretty strongly recomend you not eff with it any further until you can get a fully charged battery. again,the phone dieing when flashing a radio or hboot can easily leave you with an unrecoverable device.

since youve gotten the ruu to flash,apparetnly without error,heres what id do:

-put it aside until charged battery is available.

-run ruu again

-factory reset from hboot if it still wont boot.

failing that,you can run other ruus if youd like,since you still have no main version.
[Thunderbolt Android Development] cyberkeeper1:
i wonder if he could flash any of the froyo roms from the older RUU's? i wonder also if the program would complain of a newer hboot. if he could some how get to hboot version 1.04.0000 then there might be hope because i remember thats the one that wasnt locked up and could be exploited easily.
[Thunderbolt Android Development] scotty1223:
hboot 1.04 is no more exploitable than 1.05. revolutionarys exploit to disable WP works with either version,so as long as you can get the phone to boot with build #2.11.605.5 or older,all you need to do is run revolutionary.

there is not a way,that im aware of to exploit either hboot without a working OS or recovery. and unfortunately there is no way that i know of to get a working recovery onto an unbootable,s-on device without unlocking an htcdev compatible bootloader.

the thunderbold is old enuff its not doing an hboot version check,so without a main version to comapre to,he can flash any ruu he wants,all the way back to 1.03.605.0. although there isnt much advantage to flashing one that old.

if the phone wont boot after another ruu flash and factory reset,he could unlock hboot 1.05 and attempt to flash or boot a recovery,tho im not sure what advantage that would have. revolutionary may work in recovery to get the phone s off,but but again not sure what advantage that would have,as he can allready flash any ruu with a missing main version. flashing a rom only fixes boot and system,wich is also fixed with the ruu,so im doubtful a rom flash will change anything.
[Thunderbolt Android Development] cyberkeeper1:
Ok so then-- I highly suggest he unlocks the bootloader to install a custom recovery if possible and flash any os he wants without an ruu. Just to get something, and then run a factory rom
[Thunderbolt Android Development] Ratbastrd:
question about flashing img files. Do I need to define the partition, or specify the location?
[Thunderbolt Android Development] scotty1223:
youll need to specify the partition for the phone,and the location of the .img on the pc,unless you put the image into the adb fastboot folder:

fastboot flash partition imagename.img

i.e.,

fastboot flash recovery twrp-mecha.img

assuming an image called "twrp-mecha",thats in your adb/fastboot folder.

i think you are better off to run the ruu again and try a factory reset,than to unlock and flash a recovery at this point. wichever you decide to try,id wait for a fully chearged battery.
[Thunderbolt Android Development] Ratbastrd:
I agree, it feels like I have made some progress and the phone is still responsive. I am going to wait till I have a fully charged battery to proceed further. One other observation. While the phone is stuck in a repetitive boot sequence (white HTC screen), if I remove the battery and vol-/pwr cycle the phone the fastboot screen show hboot 1.5, and no security warning anymore. Pink locked message.
[Thunderbolt Android Development] cyberkeeper1:
I tested the reset ruu flag fastboot command with S on and locked and its worked. That means he should be able to reset the ruu flash count and wipe the cache and stuff. The command is "fastboot oem reset RUUflag"
[Thunderbolt Android Development] cyberkeeper1:
i should add though that the command was run on a spare htc vivid (holiday GSM phone) and responded.
[Thunderbolt Android Development] Ratbastrd:
Okay, battery arrived today. I ordered a battery charger as well (JIC). I have read the last couple of pages and would like to ask for your best guess to how to proceed from here.

Scotty you seem to be of the opinion that I should try a reflash and barring success, attempt a factory reset from the hboot screen? CK I read your post but am unclear how I would unlock the bootloader from fastboot? Revolutionary and Thunderbolt tool, don't recognize the device right now.

Going to install battery and try a reflash and or reset now.
[Thunderbolt Android Development] cyberkeeper1:
Yea you can put your phone in fastboot and manually unlock the bootloader again. This will allow you to install a recovery of your choice. Use 4 ext recovery for it because it charges and actually uses the charge light. And you can install whatever rom you want to establish whether or not your phone will even boot to a rom after failing a radio flash, the basis of the thunderbolt s-off exploit.

---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------

Both revolutionary and Thunderbolt tool require the phone to be first booed to utilize adb. These automated tools aren't smart and follow a script with only 2 variables and will fail if one is not met. Variable 1 is, yes its connected and visible via adb, and 2 is no its not so let's close the program.
[Thunderbolt Android Development] cyberkeeper1:
Its sounds as if the kernel didn't flash correctly. The best we can have you try is this:

Fastboot oem reset RUUflag

(resets the ruu flash count and and problems it had in the devlog. phone will reboot into fastboot or try to boot off the rom you flashed. If it tries to boot, pull the battery and enter fastboot again manually. We know it won't boot so there is no point in letting it try.)

Next, once in fastboot, select "bootloader". Hboot commands are fastboot, recovery, clear storage, etc. You need to choose clear storage to erase all of the partitions including the user data, cache, system and dalvik cache.

Try flashing the ruu one more time. If this fails again, I want you to try unlocking to bootloader via htcdev.com using your unlock token.

Fastboot oem get_identifier_token

You have the proper hboot version so unlocking temporarily to fix problems with flash partitions is important to try, and won't be a problem for you.

---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------

Dang phone app... I have to fix the post on my laptop.

Edit: got it. Never mind lol
[Thunderbolt Android Development] Ratbastrd:
Something else that is strange. I loaded the SDcard into my new S4 and attempted to move the thunderbolt RUU file to the SDcard. It will not allow me to move the file to the card. I get a cannot copy file message.
[Thunderbolt Android Development] cyberkeeper1:
Follow htcdev.com explicitly to unlock the phone. Register with a username, password and email address. When completed, you can choose your device, and you must follow exactly what it says to get it unlocked. Using automation tools won't help you because the phone can't boot.

Go here:

click here

---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------

regarding the sd card, it might be corrupt. Formatting it will fix it
[Thunderbolt Android Development] Ratbastrd:
CK, when in hboot (bootloader) screen options are:

1. Fastboot

2. Recovery

3. Factory reset

4. Simlock

5. hboot USB

6. Image CRC

I do not see a clear storage command. Do you mean factory reset? If so I have tried that.
[Thunderbolt Android Development] cyberkeeper1:
My bad man. I am in between support of like 6 different threads. The clear storage command isn't available in thunderbolt, but rather the incredible 4g.

Well, the next thing I'd try is to format the sd card if it has issues and try again. Otherwise, unlocking and downloading 4ext recovery will allow not to just remove files, but fully format the partitions since you may have a problem with flashing boot. Using standard recovery only does rm -rf which just deletes file and folders. This won't fix your issue.
[Thunderbolt Android Development] Ratbastrd:
Hey no problem you have been an extraordinary help. So I have successfully unlocked the bootloader.

Not sure if you saw my message but I tried to simply move the thunderbolt RUU to the SDcard and was going to attempt to flash using hboot, didn't work, suspect you already knew this.

Anyhow now that the bootloader is unlocked, should I attempt to flash the TB RUU again or move to the new recovery?

If new recovery, it appears that 4ext is available via goog play, is there a seperate download link or do I need to download this via my other phone. Also what process am I going to use to install (flash img?).

thanks,
[Thunderbolt Android Development] scotty1223:
it looks to me like boot flashed just fine during the ruu. i hate to say it,but its starting to look like a failing emmc,or some other sort of hardware malfunction to me.

-ruus flashed fine,phone wont boot

-factory reset with the stock recovery in place,and phone wont boot

neither of those things are good. prolly 99.9% of fixable phones are fixed by one or both of those. yall can try unlocking and installing a rom,and if youre still missing your main version,you can try running some other ruus,but at this point,you are prolly grasping at straws :(
[Thunderbolt Android Development] Ratbastrd:
By the way, pink banner says unlocked but phone still shows S-ON.

And yes I am starting to think this is a fruitless mission.

---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------

Tried the RUU again, no go this time.

C:\tbolt>fastboot flash zip Thunderbolt_2.11.605.19_PG05IMG.zip

sending 'zip' (458907 KB)... OKAY [ 76.648s]

writing 'zip'... INFOadopting the signature contained in this image...

INFOzip header checking...

INFOzip info parsing...

FAILED (remote: 33 security check fail)

finished. total time: 79.969s
[Thunderbolt Android Development] cyberkeeper1:
As far as the recovery I'm going to be getting on my laptop in just a moment to fix my other phone anyhow so I will provide you a link to the recovery flashable img file. The Google play store isn't what you need and won't work. :)
[Thunderbolt Android Development] Ratbastrd:
Scotty any thoughts on what ROM or RUU to try?

---------- Post added at 04:43 PM ---------- Previous post was at 04:09 PM ----------

Scotty, another question, can you explain to me why I cannot move these files to my phones SD card? I keep trying to move the zip files and get a cannot copy message.

It seems odd.
[Thunderbolt Android Development] santod040:
Bad formatting, or not enough room on the card?

4ext Recovery flashable via hboot: LINK
[Thunderbolt Android Development] cyberkeeper1:
you are a life saver santod.... XD i was looking EVERYWHERE for this... i was almost gonna be forced to buy the recovery control app.

---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------

didnt i mention this already? :) lol
[Thunderbolt Android Development] Ratbastrd:
Yes, you did. I kinda missed that section. Reformatting now.
[Thunderbolt Android Development] cyberkeeper1:
this error is because you are unlocked while trying to flash a signed HTC RUU file. you cant use this step yet and have to be locked. we want you to first format everything on your phone. all partitions, sd card and user space to refresh your phone's eMMC chip. that's the purpose of having you unlock again. and santod actually gave you a direct link to 4EXT, so flash away! lol. the stock OS can use EXT3 FS type but its better to use the "restore to default" option in formatting to put the phone in YAFFS2 format, which is what GB uses typically.

on a side note, i wasnt able to keep track of all the posts on my phone. i apologize if i was confusing because of this... so, unlocking the bootloader does NOT give you s-off, and never will. many more things have to be done to get to that. failed flashes mean corrupt flash file systems. using a special recovery will fix tha

as far as grasping straws, you are kind of right. its an educated guess at best in this situation when we, the users, don't have physical access to the phone. i know with patience i can have your phone working. since it accepts the RUU, its not broken. it just needs help working again. RUU wont fix a corrupt partition. if you are getting the white htc screen followed by an immediate reboot means the boot partition or kernel isnt funtioning properly. happened to my thunderbolt while trying to apply an overclocked kernel or boot.img which broke my wifi, and running the RUU actually fixed it.
[Thunderbolt Android Development] Ratbastrd:
Formatted SDcard, 32gb of space on card. Can move multiple file types to card. I cannot however move any of these PG05IMG files to the card. All of the RUU's and ROMs I have downloaded via this thread, with the exception of PG05IMG_No_hboot_2.11.605.19.zip, show up as invalid files, when I attempt to open them or view the contents. I suspect Icannot move them to the SDcard, because the system does not recognize them as valid files.

Something tells me that if I can find a stock ROM (unrooted) that I can load on my SDcard, I will be able to flash the file via hboot.

Back to 4ext recovery, how would you like me to flash this?

Extract and flash the image via fastboot?

Flash as a zip via fastboot?

load on SDcard and flash in hboot?

thanks,

---------- Post added at 05:32 PM ---------- Previous post was at 05:23 PM ----------

CK, gotcha on the formatting, see my last post (pg 29). Understood all these posts are getting confusing for me as well, no apologies.

I also agree, while not an engineer it does not appear the phone is irretrievable. I appreciate your previous offer to have me send to you, I may just do that. I prefer however (with your patience and help) to try and fix myself. This way I am learning something in the process.

So to flash 4ext, extract and flash image via fastboot, flash zip via fastboot (RUU mode or no?) or load on SDcard and via hboot?

thanks
[Thunderbolt Android Development] scotty1223:
[

it should- thats the point of an RUU. to restore all partitions to factory fresh. only exception will be partitions that dont live in flash memory(like the radios) and in those cases,the ruu flash usually fails when that partition is corrupt or damaged.

hate to say,i dont share cyberkeepers optimism in getting your phone working. bootloops are caused by lots of different things,too high a processor clock speed is just one of them. its been my experience that an incompatible kernel usually hangs at the splash screen,not bootloops. the bootlooping is an issue that plauged us(thunderbolt users) back in the early days,do some searching and youll find alot of old threads on it. no one ever really did figure it out,but the suspect cause was a failed,poor quality emmc. phones that started doing it were ultimately just swapped out for warranty excahgne.

i dont want to discoruage you from messing with it,and learning,just relaying info. id love to be wrong and see it work again :)

i must admit im pretty confused in whats going on with the jumping back and forth,so if theres anyting i missed,holler again and ill try and answer it :)

i would do this: v

flashing PG05IMG type files with s on(via fastboot/pc or hboot/sd card) can be a PITA,becasue the android info text document comes into play. of course,if you still have no main version,you are prolly exempt :p

for normal (:p) s on phones, the main version on the document must be > or = to the main version on the phone. otherwise the flash fails and causes alot of fustration.

fastboot flash recovery recoveryimagename.img is the easiest way,IMO with s on.

with the unlocked hboot,you should also try the "boot" comand again,and see if recovrry starts

fastboot boot recoveryimagename.img

and you can also try that command with your boot image(make sure to use the one from the ruu you just flashed)

fastboot boot bootimagename.img

going with the theory that boot partition is damaged and/or not being properly flashed,booting the kernel should fire it right up into the OS *if* thats the only thing stopping it. :)

edit

if the recovery wont flash or boot,its another bad sign :(
[Thunderbolt Android Development] cyberkeeper1:
well after extensive support and questions, i have determined that the phone still will boot after some flash overrides. i have some tools in my arsenal to override protection and hopefully i can receive the phone to fix it. its up to him. if i have to use brute force (figuratively speaking of course) in flashing it over i will. there are a lot of things left to try still and i managed to recover boilerman's phone out of the darkness... we all thought it was a goner too.
[Thunderbolt Android Development] Ratbastrd:
Thanks again guy's for the help. I may in fact mail the phone to CK to see what he can do, can't hurt at this point.

Unfortunately nothing seems to work right now.
[Thunderbolt Android Development] scotty1223:
Lol,based on what have you determined the phone will boot? If you have anything else up your sleeve,why don't you bring it forward so he can fix it himself? He has a good understanding of what he's doing,and is following directions well. He's quite capable of trying anything that you can think of.

I never thot boilermans phone was a goner. He just needed help with drivers and the correct ruu.
[Thunderbolt Android Development] scotty1223:
What happened when you tried to flash recovery?

What happened when you tried to directly boot recovery?(with fastboot boot)

What happened when you tried to boot the boot image?
[Thunderbolt Android Development] Ratbastrd:
All the same things, reboot to HTC white screen for 15 seconds, cycle reboot to same screen again and again.

Something is corrupted.

I am going to download the image directly to the phone today and try flashing there. It would be helpful to have copies of some earlier stock (non-root) images to try as well, but can't find any.

Also wondering if the no-hboot version used for rooting would help.
[Thunderbolt Android Development] scotty1223:
Are you looking for recovery images? or are you looking for older ruus? You can find ruus at shipped-roms.com

If you can't find it, I will get you some links later.
[Thunderbolt Android Development] cyberkeeper1:
to put it simply I cannot upload all these things because my upload is too slow. I have over 2gb of tools assembled from over time. some of them do include things already available to anyone, and some are not available now because multiupload.com is not around now. I cannot upload such a thing as no free service would take that large of a sized arsenal, and I can't spend a week in front of the computer waiting. lol
[Thunderbolt Android Development] scotty1223:
if you truly have useful tools or files,upload them for other members of the community to use.

signed,factory ruus(PG05IMG or .exe files) can be uploaded to http://shipped-roms.com/index.php?category=android&model=Mecha

tools less then 200mb can be uploaded to http://www.mediafire.com/

bigger tools or custom roms/ruus can be uploaded to http://www.androidfilehost.com/ just contact them and they will set you up

you can also get 225gb of storage with dropbox.

all the above for free. ive uploaded and downloaded alot of big files pre-high speed internet. you just do something else while the computer is busy. you dont need to sit in front of it and watch ;)

anything you can email,shoot it my way ill be happy to upload it for you
[Thunderbolt Android Development] scotty1223:
[

no hboot wont be of much use while s on. its factoru,unmodified images, 100% stock for all practical purposes,but is an insigend file,so you cant flash it. what you can do with it is unzip and remove images. with htcdev unlock,you can put together a "mini-ruu" of sorts,that will just contain boot,system,recovery,and the android info text document.

so fastboot boot boot.img yielded the same bootloop?

if you want to try other ruus,there are here:

http://shipped-roms.com/index.php?category=android&model=Mecha

and more here:

http://ruu.androidfiles.org/?developer=Mecha

i might have a couple others,if so ill get them uploaded to shipped roms.
[Thunderbolt Android Development] Ratbastrd:
Yes same results all the way around. I note however earlier in this thread that someone encountered exactly the same scenario as me with the white screen etc. He downloaded the RUU to the phone and booted into hboot. The phone flashed the image that way and solved the problem. I may not be able to do that now that I am "unlocked" via the HTC unlocker. May need to reverse that and try. Not sure
[Thunderbolt Android Development] cyberkeeper1:
yea we tried that with the recovery and apparently it only accepts kernels to use with that command. i tried that with a stock incredible 4g and used the signed recovery.img and the unlocked bootloader method of booting any other recovery and it failed. my conclusion was that these images are not boot images and it wont accept booting from them. tried it on my thunderbolt too and it also didnt work. "fastboot oem boot" or "fastboot boot boot.img" was the only thing that started the phone on both of my devices.
[Thunderbolt Android Development] scotty1223:
You are correct,you will need to relock in order to run a full,signed ruu(or any signed,official package that contains anything other than boot,system,or,recovery)

Have you tried a different sd card alltogether to try and fix your transfer prollem? Or an sd card reader,rather than another phone?