yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] boilermanAres:
It is going to Cyberkeeper1 today from NY, if you want to play with it too, I'll let you all work that out. I am putting a label in the box where to send it back to.

thanks for all your help....
[Thunderbolt Android Development] scotty1223:
its up to you. i enjoy messing with the clip and with phones,so if its something youre interested in,id be happy to do it. :)
[Thunderbolt Android Development] je2854:
you know..... I have ways of flashing the ENG hboot with NO banner and S-OFF (;

AND you can return it without losing any warranty or insurance as it looks like it came from the factory that way... JS
[Thunderbolt Android Development] scotty1223:
Sounds like a hex edited revolutionary or eng hboot. I'd personally rather have radio s off.

It is unethical IMO to return a device with a hexedited hboot,that only appears stock. With zero security checks a radio s off device can easily be returned to 100% legitimate stock,including the correct hboot for the software. JS ;)
[Thunderbolt Android Development] cyberkeeper1:
the phone from hell... or something like it.lol

its no wonder that BoilermanAres was having trouble updating it, and i will explain why. no offer to patch or hex edit applies here because he is s-on, but that's not all either. He also can't boot into the OS because there isn't one that can run with this hboot version for this phone. You need adb to run the initial root process, but you can't because there is no custom recovery or OS with which to utilize this.

So, attempting to run an RUU revealed the following:

"Invalid HBOOT Version"

Attempting to unlock the bootloader to flash a correct hboot version should fix this problem, right? oh but see there is the problem that hboot versions before 1.00 didn't include the parameter "get_identifier_token" in the sub-commands of fastboot. so that is also out the window. downloading the earliest RUU that might possibly use that version could help except that main version is higher...... So, i have been forced to attempt a JTAG operation to completely wipe out the bootloader and all its variants. that of course is extremely rash and should never be attempted unless out of options.

you know, the other option is to find the SMART_IO.CRD java control file that basically gives you s-off privileges during the time you have that file on the root of the SD card, but you cant get that either. attempting to use the build.prop file renamed as that only makes the phone freeze as it tries to read it but can't. i have noticed a gltich or what have you... when starting normally, the security warning flag pops up, but if i reboot within fastboot selection to bootloader, the warning disappears. i am going to try running the RUU that corresponds to the radio version which is update 1.03.605.10, or froyo. if i can get that part working, THEN i can re-unlock the bootloader by way of hboot exploit. my main objective is to re-write the fastboot variables to reflect the "version-main" variable, and getting an RUU to run will do just that. if i manage to make it reflect an older main version, a newer RUU should work, in theory.

As you can see, i have my work cut out for me. lol. this thing will be done no matter what. as i progress, i will update this post with pics and text. until the next time... XD

any comments are welcome during this process. :)
[Thunderbolt Android Development] scotty1223:
Unlock bootloader

Install recovery

flash zip to lower main version.

Run ruu of choice

More details and links later if you need them(not at home atm)
[Thunderbolt Android Development] cyberkeeper1:
i think you missed the part where i can't unlock the bootloader because this version doesn't support those commands. in order to unlock the bootloader i need the output from "fastboot oem get_identifier_token", but that command doesn't exist in this version of hboot. fastboot outputs

fastboot oem get_identifier_token

... INFO[ERR] Command error !!!
OKAY [ 0.013s]
finished. total time: 0.021s

i know how to do this stuff, it just isn't letting me. that's why i am posting this stuff in case i somehow miss something. i dont think i have.
[Thunderbolt Android Development] scotty1223:
Just run a newer ruu. Admittedly I've just skimmed all this while eating. I'll look a lil closer later
[Thunderbolt Android Development] cyberkeeper1:
i JUST found the right zip file. believe it or not, its not even an RUU file or zip. just an hboot flashable zip that i used in RUU boot mode to flash and main version checks out and the whole lot. WOOT!

---------- Post added at 06:19 PM ---------- Previous post was at 06:18 PM ----------

it rebooted and hboot is now up to version 1.05.0000. THANK GOD!!!

---------- Post added at 06:35 PM ---------- Previous post was at 06:19 PM ----------

ok all is done. htc RUU progress bar is full. looks like i did it right. :D [MENTION=1858440]boilermanAres[/MENTION], once i update the phone to the new OTA (if you want me to) i will send it back, otherwise, i can send it back as it is.
[Thunderbolt Android Development] scotty1223:
Glad you figured it out. :)

Just a bit of info, you can install any PG05IMG.zip file as an RUU... There is nothing special about the file.

I'd personally run revolutionary while you're on a version that you can. Once you update to hboot 1.08 you'll have to downgrade to get s off again.
[Thunderbolt Android Development] cyberkeeper1:
Well if I use the latest OTA package and rebuild it in the kitchen as a flashable zip, then it should work great, and of course that won't update hboot. :) I am getting hang of the kitchen too. One problem I that the output ROM actually ended up doubled in size exactly. I don't know what I did. Lol.

---------- Post added at 06:08 AM ---------- Previous post was at 05:43 AM ----------

Well, all things aside, it's completely stock with the latest gingerbread update. It appears to never even been unlocked and I suspect it's because of that older hboot. When I did the RUU, it didn't complain about anything and there is not a relocked warning
[Thunderbolt Android Development] jacobmacek:
people are still trying to get their bolts unrooted back to stock? whoa lol
[Thunderbolt Android Development] Ratbastrd:
Corrupted hboot (security warning)

This phone is a backup, which I would like to restore to functionality. I tried to update CWM somewhere along the way and the phone got mucked up. I have apparently lost root.

The phone is S-on

HBOOT - 1.04.2000

Pink "security warning" is on

I have modified the USB drivers and can access the phone via USB using fastboot. ADB does not recognize the phone.

I have tried to access the token and request a new one from HTC, not luck, get an error message. Essentially the only thing I can do is recognize the device via fastboot, anything other then that gives me the error msg.

Would really appreciate some help in getting this phone back so that I can stuff in a drawer and keep for emergencies.

Thanks!!!
[Thunderbolt Android Development] santod040:
What happens when you try flashing a stock RUU from hboot?

Device powered off:

Stock GB RUU(no hboot) on the root of sd card named PG05IMG.zip (hboot onlyif needed for any reason)

Hold volume down + Power until the white screen come up

It should find the rom image and ask to update and allow you to confirm or deny via volume rocker.

Does that not work for you? What happens when you try?
[Thunderbolt Android Development] Ratbastrd:
I don't recall the specific message but the phone would not flash it, it ran the check and gave an error message. I am able and effectively stuck in the hboot (white) screen. Phone will not power off, phone wont charge (thing the battery stats are mucked up as well). As soon as I plug in the phone boots to the flashboot screen and flashes the pink security warning sign.

I am trying to flash via hboot right now. I think if I can get the battery charged, I can flash via hboot. The question at that point is which image to flash to get back to a point where I can run one of the root methods.

Screen capture:

Pink Security Warning on top

MECHA XD ENG S-ON

MICROP-/

RADIO-1.49.00.046w_1

eMMC-boot

Feb 23 2011
[Thunderbolt Android Development] santod040:
If you can flash the RUU I posted, then you can run the all in one tool to root.
[Thunderbolt Android Development] cyberkeeper1:
in order to flash a specific stock rom for htc, you MUST be in RUU, and you must be locked (however you seem to already be based on the fact that you have a security warning). hboot flashing doesn't always work and sometimes skips the file altogether even if its valid, but may sometimes be off by a few bytes of data. we all know this hassle. :"scanning zip...Parsing zip" and then does nothing and goes to the boot selection menu. what is CRC of the ROM you have, Ratbastrd? because i already fixed BoilermanAres' phone using my zip. i need to upload the zip i used for RUU, or try santod's zip file as i am very confident that he also has a working RUU zip file. this post you should be able to get the phone to stock. you must flash the rom twice because the first time it flushes HBOOT and overwrites it with a new one.

in essence, do this:

Flash the correct ZIP file in RUU mode (you must be in RUU mode. you will see a black background with a white HTC logo.)

reboot to RUU(fastboot parameters are case sensitive... you must follow the case entirely):

fastboot oem rebootRUU

flash the RUU:

fastboot flash zip RUU.zip

(it can be named whatever and should be all one word)

after flashing the zip, you will get this error:

at this point, do nothing and reboot the phone again directly to RUU to parse the new HBOOT 1.05.

fastboot oem rebootRUU

then flash the zip again:

fastboot flash zip RUU.zip

you should see the output commands giving every line as "INFO" telling you what has been done correctly.

thats it. you want to make sure that you are using the right drivers too. you can use the drivers here on the first page, or the universal naked drivers (version 0.72) found on XDA. just search for it. (trying to emphasize the use of search here on the forums... :D)

so if everything turns out fine, turn on your USB debugging once the ROM and setup loads and root away if that is what you want. make sure you use the latest root and s-off method provided by Revolutionary for the safest method.

---------- Post added at 11:56 PM ---------- Previous post was at 11:53 PM ----------

even though it saysto immediately flush, i always reboot for safe keeping.
[Thunderbolt Android Development] scotty1223:
your hboot version is a little off... ive never heard of that version. the s-off eng hboot is 1.04.2000,so sounds like youre either s-on,1.04.0000 or s off 1.04.2000.

all you need to do is run a newer signed ruu than whats on your phone. with s on,you cant run something older,and you cant run an unsigned file(i.e. no hboot or hboot only from the OP)

we need to know your main version. put phone in fastboot,open cmd,and enter:

fastboot getvar mainver

or

fastboot getvar all

and paste results here.

well,this is not entirely true. RUU mode is one way to skin the cat,but not necessary. it is my personal favorite way to run ruus,as .exe files can be finicky,and using hboot requires correct name and sd card format,wich sometimes throws people for a loop(i.e returning silently to the hboot screen without updating if the signiture,name or format is wrong)

the phone does several security checks- main version,model id,signiture,cid,etc. so a particular ruu isnt going to fix every phone in every case.

the security warning appears with newer hboots when an ruu attempt is made,and the flash fails initially with an hboot pre-update,and the hboot realizes that the software on the phone is not what expects(usually a custom rom,but could also be triggered by older or newer stock stoftware).

once the main version is known,all thats needed is to run that ruu or newer,by any means available.

fastboot getvar all will tell generally everything needed to know about the device :)
[Thunderbolt Android Development] Ratbastrd:
Scotty, this is really helpful. After many hours on this last night, I have determined the following. A) battery is dead needs to be replaced. B) I am probably best off choosing the latest RUU, as this would give me the greatest probability of successfully overcoming the current state?

Thanks again!!!!
[Thunderbolt Android Development] Ratbastrd:
Fastboot getvar all results:

C:\tbolt>fastboot getvar all

INFOversion: 0.5

INFOversion-bootloader: 1.04.2000

INFOversion-baseband: 1.49.00.0406w_1

INFOversion-cpld: None

INFOversion-microp: /

INFOversion-main:

INFOserialno: HT15SS001216

INFOimei: 355195000000017

INFOproduct: mecha

INFOplatform: HBOOT-7630

INFOmodelid: PG0510000

INFOcidnum: VZW__001

INFObattery-status: low

INFObattery-voltage: 3367mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: ENG

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: 9a13ccd2

INFOhbootpreupdate: 12

INFOgencheckpt: 0

INFOregion-id: not support

all: Done!

finished. total time: 0.012s

PS: I believe the problem occured when trying to update the recovery to a newer version of CWM. This was a while ago so details are a little fuzzy.
[Thunderbolt Android Development] scotty1223:
Wow... That's weird. I have never seen that before. What happens if you try and boot to recovery? The good news is that you should be able to run any full,signed ruu that you want. Your main version is blank
[Thunderbolt Android Development] cyberkeeper1:
yeah I saw that too I was thinking the same thing. Boilerman had the same problem with the main version being blank when I tried to retrieve it. I do not know for sure because I didn't design it, but I think when Hboot gets downgraded during s-off process, it erases the main version variable. It's the third one I've seen so far and each person was trying to root and unlock their phone

---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------

Yep, these phones are still rockin
[Thunderbolt Android Development] scotty1223:
ive seen the blank main version a few times,also seen a "generic" main version,i.e. 3.14.0.0 instead of 3.14.605.5. in some cases i think htc installs the generic main version so a particular ruu will still flash. the missing ones are likley the result of hacking,or some malfunction.

the wierd part to me,is the hboot... its almost an oxymoron. the "2000" has been typically used for eng(engineering) version numbers,and even the version says "eng" but then "s-on" :confused:

i wish there was some way you could dump it before you flash something different.

i thot maybe it was a hex edited eng s off hboot,but the security pretty plainly shows "on". hmmm.
[Thunderbolt Android Development] Ratbastrd:
In my case, I believe I was updating the recovery. It seem like something is causing a conflict with the bootlock work around.

---------- Post added at 07:44 AM ---------- Previous post was at 07:38 AM ----------

I can try to get a dump if you will give me some instructions.
[Thunderbolt Android Development] scotty1223:
What state is the phone in? You'd need to be able to boot to a recovery with an adb daemon running,or an OS with root access
[Thunderbolt Android Development] Ratbastrd:
The unit is stuck in the fastboot/hboot mode. I have modified the USB drivers and have connectivity with the phone but only through fastboot. I can get the phone to RUU mode and move the PG05IMG file to the phone but cant flash because the battery is too low. The phone wont power down. As soon as I plug the phone in, it boots to the fastboot screen. I have a new battery coming, which will allow me to reflash the new RUU.

I have tried getting the phone to recovery, nothing happens.
[Thunderbolt Android Development] scotty1223:
Can you get an output from:

Fastboot oem ?

(? Is part of the command)
[Thunderbolt Android Development] Ratbastrd:
fastboot oem ? (results)

INFOmb

INFOmh

INFOmw

INFOew

INFOeh

INFOeb

INFOmmu

INFOram_test

INFOjump

INFOtest

INFOsdtest

INFOeraseconfig

INFOwriteconfig

INFOreadconfig

INFOwritesku

INFOreadsku

INFOrflash

INFOtflash

INFOblock_test

INFOpartition_test

INFOrbchk

INFOerasesd

INFObtrouter

INFOtick

INFOheaptable

INFOemapi

INFOemapiTest

INFOemapiCountryID

INFOemapiWlanMac

INFOemapiSetDefCal

INFOemapiReadCal

INFOlr

INFOimgcrc

INFOresetautoimage

INFOresetpreferdiag

INFOresetRUUflag

INFOwriteserialno

INFOreadserialno

INFObattcheck

INFOgotofastboot

INFOgotohboot

INFOwritemid

INFOusbtestmode

INFOeraseWifiFlash

INFOerase

INFOreadmbserialno

INFOlistpartition

INFOerasebcid

INFOwritebcid

INFOreadbcid

INFOfmrouter

INFOfmtx

INFOresetuP

INFObdaddress

INFOwMfgTp

INFOrMfgTp

INFOemptypagecheck

INFOsaveprt2sd

INFOsavemem2sd

INFOsavefb2sd

INFOemapiInit

INFOemapiChannel

INFOemapiBand

INFOemapiRate

INFOemapiRateset

INFOemapiCountry

INFOemapiTXpwr1

INFOemapiPkteng_start

INFOemapiPkteng_stop

INFOemapiOut

INFOemapiFqacurcy

INFOemapiCrsuprs

INFOemapiUp

INFOemapiDown

INFOemapiMpc

INFOemapiCounters

INFOemapiVersion

INFOemapiEtheraddr

INFOemapinRate

INFOemapiSetIrqPin

INFObkflash2emmc

INFOfl

INFOloaddiag

INFOlnb

INFOinit_a1026_fw

INFOcheckKeyCard

INFOusbspeed

INFOgpiow

INFOgpior

INFOmddiw

INFOmddir

INFOclock

INFOi2cr

INFOi2cw

INFOi2ctest

INFOulpi

INFOchangeCid

INFOread_l2_acc_fuse

INFOqupi2cr

INFOqupi2cw

INFOpmgpiow

INFOpmgpior

INFOdgtest

INFOentpa2051

INFObumpclk

INFOswitch_ddrfeq

INFOntrigsetcal

INFOltetest

INFOsdio_loopback

INFOsdio_setsize

INFOsdio_readblk

INFOsdio_writeblk

INFOsdio_readblk

INFOsdio_dumpreg

INFOemmc_boot

INFOfdisk_emmc

INFOset_partition_emmc

INFOerase_emmc

INFOtest_emmc

INFOsector_erase_emmc

INFOfat_format_emmc

INFOinit_emmc

INFOreinit_emmc

INFOwrite_emmc

INFOupdate_ptable_emmc

INFOset_wp_emmc

INFOwrite_prot_test

INFOclear_wp_emmc

INFOset_enh_area_emmc

INFOkeytest

INFOheap

INFOboot

INFOreset

INFOpowerdown

INFOrebootRUU

INFOheap_test

INFOrtask

INFOtask

INFOenableqxdm

INFOgencheckpt

INFOlist_partition_emmc

INFOload_emmc

INFOcheck_emmc

INFOcheck_emmc_mid

INFOread_emmc

INFOget_wp_info_emmc

INFOsend_wp_info_emmc

INFOget_ext_csd_emmc

INFOget_sector_info_emmc

OKAY [ 0.151s]

finished. total time: 0.151s
[Thunderbolt Android Development] scotty1223:
That's awesome. Looks like you have the full list of.eng commands. I wonder if you have less limited security than normal ship hboots... When you get your battery try and fastboot boot or fastboot flash a recovery. I'd hate to run an ruu without making an effort to make a copy of it
[Thunderbolt Android Development] Ratbastrd:
I've tried flashboot boot, no luck just brings me back to this screen.

Re flashing a recovery, what would you recommend?

Any risk of further complication by doing this?

If the unit is in fact locked, it shouldn't allow me to flash a recovery right? What should happen?

If I am able to flash a recovery will the unit then allow for battery recharge? I don't have an external charger so I am limited to the amount of power in the new battery when it arrives.

thx
[Thunderbolt Android Development] scotty1223:
Yes,if you could get a recovery,it should charge.

Typically on an s on device,correct it would not let you flash recovery. but,typically an s on hboot does not have all those extra commands. So,maybe the securities are less.

No further risk that I can think of. It will prolly just fail,leaving you no worse off ;)

Put.recovery image into fsdtboot/adb folder and:

to boot:

Fastboot boot imagename.img

To flash:

Fastboot flash recovery imagename.img

Sorry my lack of detail,I'm on my phone... No pc available until tomoro sometime
[Thunderbolt Android Development] cyberkeeper1:
TWRP offers charging... XD

twrp's open recovery 2.5 allows charging most definitely. i was rooting my phone again to get s-off and noticed it was charging. so i actually had no idea you could boot from an image without actually flashing it. what is the purpose of that? does that even work while s-on?
[Thunderbolt Android Development] Ratbastrd:
Downloaded TWRP for Thunderbolt. Moved to folder, renamed PG05IMG.

Attempted to boot per instructions above. Received the following

C:\tbolt>fastboot boot PG05IMG.zip

creating boot image...

creating boot image - 4972544 bytes

downloading 'boot.img'... OKAY [ 0.793s]

booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)

finished. total time: 0.829s

---------- Post added at 07:12 PM ---------- Previous post was at 07:09 PM ----------

Attempted to flash recovery

C:\tbolt>fastboot reboot

rebooting...

finished. total time: 0.159s

C:\tbolt>fastboot erase cache

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

finished. total time: 0.212s

C:\tbolt>fastboot flash recovery PG05IMG.zip

sending 'recovery' (4853 KB)... OKAY [ 0.789s]

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

FAILED (remote: signature verify fail)

finished. total time: 1.598s
[Thunderbolt Android Development] cyberkeeper1:
Yea then just go ahead and run the RUU zip I am uploading. You are s-on, and that won't change until you acquire root access again. In fact, my file is almost done. It's uploading at like 110-150 Kbps. Last time I checked it was 28% done over an hour ago.
[Thunderbolt Android Development] scotty1223:
You can't fast boot flash a zip. Take the image inside out,fast boot flash that.

Fastboot flash recovery imagename.img

Or

Fastboot boot imagename.mg
[Thunderbolt Android Development] cyberkeeper1:
hey here is the dev-host link to download my file:

http://d-h.st/28d

---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------

hey here is the dev-host link to download my file:

http://d-h.st/28d
[Thunderbolt Android Development] Ratbastrd:
Okay, did not know that, sorry capable noob, but noob all the same.

Attempted to boot the TWRP recovery after extracting the recovery to the fastboot folder.

Received the following.

C:\tbolt>fastboot erase cache

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

finished. total time: 0.210s

C:\tbolt>fastboot boot recovery.img

downloading 'boot.img'... OKAY [ 0.797s]

booting... OKAY [ 0.001s]

finished. total time: 0.799s

Interestingly enough when I attempted to then open recovery, The phone tried to flash a PG05IMG file that obviously is sitting in the directory. Got a battery warning, couldn't flash. Is there anyway to access the directory to remove whatever zip file is sitting in there? If not how am I going to be able to override this and flash the RUU I want? Sorry if this questions are a little rediculous.

thanks,

---------- Post added at 10:09 AM ---------- Previous post was at 09:42 AM ----------

Guy's I spent some time rereading this thread and am a little confused. One person is saying that zip files can be flashed from fastboot the other is not.

I have tried several things today none of which work, which raises the question of what can and cannot be flashed.

So I have downloaded cyberkeepers RUU. When attempting to flash the entire zip file in RUU, I get the battery warning and error message previously documented.

When I follow scotty's directions and pull the system image out and try to flash the system image, I get

C:\tbolt>fastboot flash image system.img

sending 'image' (882684 KB)... FAILED (remote: 02 data length is too large)

finished. total time: 0.004s

So it appears that trying to send the entire image file uncompressed is not going to work.

Confused and a little concerned. When i get my new battery I am only going to have so much charge to work with before I end up back in this state.

thanks guy's!!!
[Thunderbolt Android Development] scotty1223:
Hmm very interesting. From your cmd output looks like the recovery should have started. Did you try and fastboot flash it as well? It does appear your eng s on hboot does have some different securities than what were used to. I

The rest of your questions need a level of detail I can't really go into on my phone... I'll have a response for you later.