Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.498s
Thanks!
JMBush1007 said:
Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.498s
Thanks!
Click to expand...
Click to collapse
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
acejavelin said:
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
Click to expand...
Click to collapse
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Glad you got your answer! Also, cloning your IMEI and ESN is illegal and a major criminal offense. I suggest you don't go down that route.
JMBush1007 said:
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Click to expand...
Click to collapse
The result you got with rumrunner is very common, not sure exactly what it corrupts (probably the boot partition) but it is common to for it to freeze/bootloop after going S-OFF, as long as it's S-OFF in the bootloader, it is S-OFF... there is no "kinda S-OFF". Just restore the backup you did before running rumrunner (you did a Nandroid first, right ) or reflash your ROM and Gapps, no worries, this is kinda normal.
As far as the "most stable" ROM, this seems to vary a lot on the person, configuration/apps, ROM, and hardware build, some ROMs are better than others under various conditions and trial and error is the only real way to find out. Some Rezounds just do not like KitKat, others don't like JellyBean, etc... so if are having lots of issues with one, try a different one. A few ROMs you didn't mention that I think are very good on the Rezound are EclipticRez Revamped v9 (this is the most stable non-stock ROM I tried) and Nils Business Sense that are both ICS based, Beanstalk and Talon are two really good under-rated JellyBean ROMs just remember that some JB ROMs can swap your internal and external storage around in mounts (they appear swapped when the phone is booted, this is not really a bug if you see it). But to be honest, if you are flashing http://forum.xda-developers.com/showthread.php?t=2260154 or gone through @REV3NT3CH's full downgrade/upgrade guide and are still having issues, it could very well be hardware issues.
And yes, @kcipopnevets is correct... ESN/MEID swapping is illegal, although I don't know how much of a "major criminal offense" it is. But generally it is considered fraudulent activity and a violation of your terms of service on your cellular plan as well.
Related
Alright,
I recently rooted, S-Off'd, custom rom'd my Amaze for T-Mobile. The process went very smooth, as I've done this for several phones that I've owned in the past (Sensation, G2X, N1, G1).
I decided that I'd like to have an OC'd Kernel that would also allow for undervolting, and went with what appears to be the only Kernel offered on this device: Faux's123.
I flashed it through 4ext whilst on the Speed 6.5 rom, and ran some Quadrant and Antutu benches to see if it stuck, and it was awesome.
Now comes the problem, when I awoke yesterday, my phone was boot-looping. It did it from the moment I woke until 5 hours later when it died... I've done everything I can think of, or have read to remedy the situation. I've factory data reset it through 4ext, I've flashed new roms, I've flashed stock roms, I've tried my damnedest to flash a stock kernel (can't find one), I re-locked my bootloader.... nothing stops it from this continuous boot loop.....
Someone please help!
The craziest thing about it is, after about 90k boot loops, sometimes it settles, and works....until I unlock the screen, and bam, boot loops again.
dlamb4prez said:
Alright,
I recently rooted, S-Off'd, custom rom'd my Amaze for T-Mobile. The process went very smooth, as I've done this for several phones that I've owned in the past (Sensation, G2X, N1, G1).
I decided that I'd like to have an OC'd Kernel that would also allow for undervolting, and went with what appears to be the only Kernel offered on this device: Faux's123.
I flashed it through 4ext whilst on the Speed 6.5 rom, and ran some Quadrant and Antutu benches to see if it stuck, and it was awesome.
Now comes the problem, when I awoke yesterday, my phone was boot-looping. It did it from the moment I woke until 5 hours later when it died... I've done everything I can think of, or have read to remedy the situation. I've factory data reset it through 4ext, I've flashed new roms, I've flashed stock roms, I've tried my damnedest to flash a stock kernel (can't find one), I re-locked my bootloader.... nothing stops it from this continuous boot loop.....
Someone please help!
Click to expand...
Click to collapse
Flash a Stock RUU, just get the one for your carrier in Krook6023's thread. Make sure you get the RUU, not the OTA.
Or if you're lazy, use this tool that I made.. http://forum.xda-developers.com/showthread.php?t=1762936
Downloading your tool now, but DevHost? Sooooo slow lol! I guess beggars can't be choosers!
2 hours from now is wayyyy better than an indefinite period of time for a fix lol.
Will let you know as soon as it's done.
Keylogger_0 said:
Flash a Stock RUU, just get the one for your carrier in Krook6023's thread. Make sure you get the RUU, not the OTA.
Or if you're lazy, use this tool that I made.. http://forum.xda-developers.com/showthread.php?t=1762936
Click to expand...
Click to collapse
dlamb4prez said:
Downloading your tool now, but DevHost? Sooooo slow lol! I guess beggars can't be choosers!
2 hours from now is wayyyy better than an indefinite period of time for a fix lol.
Will let you know as soon as it's done.
Click to expand...
Click to collapse
Really? I've never thought devhost as a slow source.
I downloaded ruu and put on 3 flash drives my external and my sd
Sent from my Energized Amaze 4G
Yes girls know about XDA
you can thank a girl on here
Keylogger_0 said:
Really? I've never thought devhost as a slow source.
Click to expand...
Click to collapse
sometimes it is... right now, i get 600kbytes/s, but at night, maybe 60-100kbytes/s... my top speed on speedtest.net is roughly 20MBit/s = 2.5mbytes/s
paperWastage said:
sometimes it is... right now, i get 600kbytes/s, but at night, maybe 60-100kbytes/s... my top speed on speedtest.net is roughly 20MBit/s = 2.5mbytes/s
Click to expand...
Click to collapse
Speed test may show 20mbps but the actual download speed is actually around 2mbps tops, for every 1mbps bandwidth speed the avg download speed is around 100kbps (more or less), so don't be fooled by speedtest, that just tells you what your bandwidth speed is, not actual download speed.
On the op question, just use keylogger's tool and restore to stock, you'll need to unlock your bootloader back for it to work, also for the custom kernel to work and avoid any bootloops, simply go in to the governor and choose either one of two things, a governor that uses regular voltages or one that doesn't OC too high, those two are the main causes of bootlooping and crashes on custom kernels, some devices can't handle one or the other or some times both.
I guess I'm just having the worst luck in the world right now....
After unzipping the ToolV2.zip file using WinRar, I double click on the RUN-ME.exe file, and get an error......
It says that it is NOT compatible with my version of Windows. I have to have a 32 or 64 bit version.... I have Windows 7 Ultimate 32-bit.... WTF!
Dark Nightmare said:
Speed test may show 20mbps but the actual download speed is actually around 2mbps tops, for every 1mbps bandwidth speed the avg download speed is around 100kbps (more or less), so don't be fooled by speedtest, that just tells you what your bandwidth speed is, not actual download speed.
On the op question, just use keylogger's tool and restore to stock, you'll need to unlock your bootloader back for it to work, also for the custom kernel to work and avoid any bootloops, simply go in to the governor and choose either one of two things, a governor that uses regular voltages or one that doesn't OC too high, those two are the main causes of bootlooping and crashes on custom kernels, some devices can't handle one or the other or some times both.
Click to expand...
Click to collapse
dlamb4prez said:
I guess I'm just having the worst luck in the world right now....
After unzipping the ToolV2.zip file using WinRar, I double click on the RUN-ME.exe file, and get an error......
It says that it is NOT compatible with my version of Windows. I have to have a 32 or 64 bit version.... I have Windows 7 Ultimate 32-bit.... WTF!
Click to expand...
Click to collapse
My apologies. That must be an error on my side. I've recompiled it with a 32 bit compiler. I plan to do a complete rebuild though.
Instructions:
Extract the zip file with your favorite file extraction utility.
Replace the RUN-ME.exe file with the 32 bit version, which can be found attached on this post.
Run the file as you normally would, and follow my directions posted on the thread.
And as the other poster said, make sure you're bootloader unlocked.
Thanks for all of the help!
Ran into another problem though, whilst running the program, it now tells me that my device is not S-Off, when Hboot clearly says so... I did the wire trick and all. Not sure, what the problem is now!
Could it be that this problem is derivative of the fact that my Hboot is locked?
Keylogger_0 said:
My apologies. That must be an error on my side. I've recompiled it with a 32 bit compiler. I plan to do a complete rebuild though.
Instructions:
Extract the zip file with your favorite file extraction utility.
Replace the RUN-ME.exe file with the 32 bit version, which can be found attached on this post.
Run the file as you normally would, and follow my directions posted on the thread.
And as the other poster said, make sure you're bootloader unlocked.
Click to expand...
Click to collapse
dlamb4prez said:
Thanks for all of the help!
Ran into another problem though, whilst running the program, it now tells me that my device is not S-Off, when Hboot clearly says so... I did the wire trick and all. Not sure, what the problem is now!
Could it be that this problem is derivative of the fact that my Hboot is locked?
Click to expand...
Click to collapse
It shouldn't be, as the script detects your S-Off state by doing the command fastboot getvar security.
It wouldn't matter if your device was locked or not. Apparently to the tool, it thinks your phone is S-On.
This is strange. Here's what I want you to do.
Click on the ToolV2 folder (don't go in that folder however), then while holding shift, right click. There should be an option that says "Open command window here"
After you've done that, it will automatically open command prompt, routed to that folder. While in that command prompt window, type in "fastboot getvar all" without quotes (Ensure your phone is booted into fastboot mode first! Also make sure your phone is connected too!)
After you typed it, press enter. The results should show up.
What I want you to do is take a screenshot of that command prompt window. (You can do this with the windows' snipping tool) And attach it. I will look at it and try to figure out.
This is what I got:
C:\Users\Don\Desktop\ToolV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: SH23PVP01066
(bootloader) imei: 358927046036465
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.505s
Keylogger_0 said:
It shouldn't be, as the script detects your S-Off state by doing the command fastboot getvar security.
It wouldn't matter if your device was locked or not. Apparently to the tool, it thinks your phone is S-On.
This is strange. Here's what I want you to do.
Click on the ToolV2 folder (don't go in that folder however), then while holding shift, right click. There should be an option that says "Open command window here"
After you've done that, it will automatically open command prompt, routed to that folder. While in that command prompt window, type in "fastboot getvar all" without quotes (Ensure your phone is booted into fastboot mode first! Also make sure your phone is connected too!)
After you typed it, press enter. The results should show up.
What I want you to do is take a screenshot of that command prompt window. (You can do this with the windows' snipping tool) And attach it. I will look at it and try to figure out.
Click to expand...
Click to collapse
dlamb4prez said:
This is what I got:
C:\Users\Don\Desktop\ToolV2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: SH23PVP01066
(bootloader) imei: 358927046036465
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.505s
Click to expand...
Click to collapse
Then you should not get an error relating to your S-Off state. It states that your security state is off, which is normal for S-Off. Are you sure you don't have any other phones connected? I know this is a silly question, but I'm not sure how you're getting that problem
Do this command "fastboot getvar security"
It should just display this:
(bootloader) security: off
My script was designed to read that statement and detect whether it says off or not. For some reason, it's not detecting that phrase, "off".
As I said, I plan to do a rewrite. This tool still should work nonetheless.
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *removed*
(bootloader) imei: *removed*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.058s
I am stuck, I can't see to get my phone to boot. You would think that I would be able to do something to fix this if I can get into recovery and bootload, but I can't get a proper system boot. I am hoping that buying a new phone isn't my only option at this point. If anyone can help me I am willing to pay if you can help me get a working phone again.
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
GPE firmware
jball said:
@Jameskhunter
You should edit your IMEI number out of your getvar
What exactly happened when you flashed the firmware ,any specific message that came across that you can remember
According to the getvar it looks like you flashed the GPE lollipop firmware/ruu without
S-OFF.
---------- Post added at 03:47 AM ---------- Previous post was at 03:37 AM ----------
Try this .exe of the stock ruu sense your At&t
http://forum.xda-developers.com/showthread.php?t=2860423
Click to expand...
Click to collapse
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Hi
Jameskhunter said:
That is what I have been told although I didn't realize that it was GPE and I don't really understand why it let me get my phone in an usable/unrecoverable state if I had s-on. I thought that was a safety net, but the more I read I wish it was s-off. I think it would be fixable then, but in the current state I don't know how to get s-off. I did the firmware command twice and it seemed to work after the second attempt as the article noted that it would. I have never flashed a rom, before so other than reading the article and attempting to follow along didn't really know what to expect. The article had me do a fastboot oem lock and then a fastboot oem ruu as I recall. then it was something like fastboot flash zip .....zip. The problem is the roms that I have attempted to install now don't seem to install maybe if I could find the right one it would install and work good enough to allow me to become s-off and get back to more of a working state. I should of done a lot more reading before attempting this... I made some invalid assumptions about being able to recover which is my fault. I would think something is possible in this state.
I think part of the problem is that I am s-on and my main ver is higher than the RUU for my carrier version and my cid. I think I could edit those if I was s-off or do something, but I can't do that since I am s-on.
Click to expand...
Click to collapse
I have tried that RUU and it fails, I think because its main version number is lower than mine now... Which I also didn't realize was a limitation. I think the lesson here is to never flash firmware that isn't directly from the htc site although its suppose to be signed, that's a little confusing to me.
I to thought S-ON was supposed to be a safety net
What Roms have you tried sense then
If you hold power+up your phone hard restarts. then quickly hold power+down. then go to recovery. If have TWRP and this way you accessed it. you got some chance. go to https://download.cyanogenmod.org/?device=m8 and download latest nightly and see if you can flash it. That worked for me. Until I find a signed firmware/radio that is version 4.+ I am stuck with cm12.
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Please let me know if you find any solution or working ROM, I tried all the links and they are all down
Koncrete said:
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Click to expand...
Click to collapse
I just got a pure stock sprint 3vo already on that OTA version and had no issues with the htcdev unlock. I had to use it to root and get the MSL, or at least kinda needed it and Sprint had no interest in giving it to me without an active account.
have you been using the window$ .exe RUUs or the PG86IMG.zip files you put on the root of the sdcard before starting the phone to the bootloader? I've had better luck with the .zip files (well, honestly, I've never run a window$ RUU except in a virtual machine just to extract the zip anyway.)
when you flash the RUU from sdcard, you get error messages on screen (if any) which likely make more sense than whatever the .exe might spit out.
perhaps I can help, though I'm not on the forums a lot these days. PMs should pop up in my email to get my attention, but any tech support I'll respond in the thread so others can benefit from the info.
I also have a functional USPS mailbox for more serious debugging, I feel that I'm fairly honest and already have a plethora of other phones anyway (I believe 2 functioning Virgin 3vos and now one Sprint branded one have joined my collection of Android hacking-at toys.)
imraxy said:
Please let me know if you find any solution or working ROM, I tried all the links and they are all down
Click to expand...
Click to collapse
a lot of the external hosting sites have gone belly-up, or worse, like androidfilehost, they deleted everything old. I lost tons of files when they decided to purge with absolutely no warning and all I can figure out is that it had something to do with the age of the uploads, because it wasn't just my files that went AWOL.
for working ROMs, there's some older ones here and more goodies here (RUUs)
and the last LiquidSmooth kitkat is here
bear in mind you may have to find the original ROM threads for the archived ones above to know which HBOOT (and maybe even radio) you need to use for each. the 3vo is picky about those.
the mods hopefully won't get uppity about me cross-forum posting, since they already destroyed the organization of the evo 3d forum here by combining general threads with both of the entire CDMA and GSM development subforums at some point in time I missed seeing until it was too late.
for the 3d forum here, this thread is particularly useful.
Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 10-13-12
this post here (linked from inside the one just above) has all the HBOOT zip files too.
Koncrete said:
im one of the ones that took the last OTA 2.95.651.6 that cant use the htcdev unlock... I get a response that it worked but I never get the accept on my phone. I am also stuck in a bootloop right after the sprint logo so I cant even verify if oem unlock or debugging are on...
Ive tried every ruu I could find for any 3d and all of them fail for different reason. The only fix I am aware of is applying the ota again but as far as I know that was never released... Any ideas? Im not afraid of braking it as its a funny looking paperweight right now...
Click to expand...
Click to collapse
you should also be able to see if it's unlocked or not in the bootloader itself in the text at the top of the screen. It'll say locked or unlocked. if it's unlocked but s-on, RUUs will fail to install.
if so, put it in fastboot from the bootloader and
fastboot oem lock
then it should accept the current RUU to match the OTA you took.
So as the phone sits now it hangs at the Sprint logo until the battery runs out or I reset it.
it is S-ON and Locked......
I cannot verify if debugging is enabled (Pretty sure it isnt)
Bootloader unlock.bin command says its successfully sent the unlock file from HTCdev with a sending time of 0.0, The dialog never shows on my phone to unlock and the bar on the right that is supposed to show the status of updates and such never comes on
Ive tried relocking and then unlocking
Ive tried from win7 32/64 os's and windows 10 64.
Ive also done this using USB 2.0, 3.0 and 3.1 slots as well as others.
I've used a known good samsung cable and a couple of off brand cables
Ive tried with and without the fastboot registry fix for HTC and mixes of fastboot/adb from everywhere
Koncrete said:
So as the phone sits now it hangs at the Sprint logo until the battery runs out or I reset it.
it is S-ON and Locked......
I cannot verify if debugging is enabled (Pretty sure it isnt)
Bootloader unlock.bin command says its successfully sent the unlock file from HTCdev with a sending time of 0.0, The dialog never shows on my phone to unlock and the bar on the right that is supposed to show the status of updates and such never comes on
Ive tried relocking and then unlocking
Ive tried from win7 32/64 os's and windows 10 64.
Ive also done this using USB 2.0, 3.0 and 3.1 slots as well as others.
I've used a known good samsung cable and a couple of off brand cables
Ive tried with and without the fastboot registry fix for HTC and mixes of fastboot/adb from everywhere
Click to expand...
Click to collapse
I've never used windows to flash an HTC, but if you downloaded fastboot from htcdev and their chunk of junk software that contains the drivers (htc sync or something, I forget) that part shouldn't matter (maybe)
you can get to the bootloader, so the phone isn't bricked.
to test the cable, you could try "fastboot getvar all" and see if there's output.
definitely no USB3 from what I've read, the phone predates that being in common use and the unlimited.io wire trick instructions say it's a no-no, they suggest the stock HTC cable too, but I used a solid offbrand cable to s-off, so the cable's not critical as long as its communicating.
try this RUU from here
put it on sdcard named PG86IMG.zip and put the phone into the bootloader (volume down while powering on.)
That'll at least get Windows out of the equation.
AndroidForums said:
How to use a PG86IMG.zip file!
SPOILER
1. Place the file on the root of your sd card (not in any folders).
2. Rename the file to PG86IMG.zip
3. Reboot into bootloader.
4. When asked to update, say yes by hitting volume up.
5. When it's all finished, hit power button to reboot.
7. *Important! After booting up, immediately rename or delete the file.
Click to expand...
Click to collapse
Let me know if that errors out or something. It's the best way to flash an RUU.
Main version is older....
[15:47:25] (bootloader) version: 0.5
[15:47:25] (bootloader) version-bootloader: 1.58.0000
[15:47:25] (bootloader) version-baseband: 1.09.00.0108
[15:47:25] (bootloader) version-cpld: None
[15:47:25] (bootloader) version-microp: None
[15:47:25] (bootloader) version-main: 2.95.651.6
[15:47:25] (bootloader) serialno:
[15:47:25] (bootloader) imei:
[15:47:25] (bootloader) product: shooter
[15:47:25] (bootloader) platform: HBOOT-8260
[15:47:25] (bootloader) modelid: PG8610000
[15:47:25] (bootloader) cidnum: SPCS_001
[15:47:25] (bootloader) battery-status: good
[15:47:25] (bootloader) battery-voltage: 3800mV
[15:47:25] (bootloader) partition-layout: Generic
[15:47:25] (bootloader) security: on
[15:47:25] (bootloader) build-mode: SHIP
[15:47:25] (bootloader) boot-mode: FASTBOOT
[15:47:25] (bootloader) commitno-bootloader: dirty-3f645641
[15:47:25] (bootloader) hbootpreupdate: 11
[15:47:25] (bootloader) gencheckpt: 0
ive tried running it from recovery for funz as well an I get "Invalid operation" oem=00
hm, maybe my sprint 3vo let me flash that because it's s-off , but if you can't even get it to flash that RUUzip off the sdcard with the bootloader, all I can think of is digging into the unbrick thread and getting creative.
or replacing it with a cheapie off ebay, my sprint model was under $7 shipped from eBay and moving the main board into one with a good screen...
within the week I intend to post a lineage 11 kitkat current build so the browser works on https, unlike any of the vintaged roms which are still downloadable, if you want incentive.
if you give up on yours, I'm game to poke at it, rather than it going in the refuse...
I've got some experience with this phone and reviving uppity devices.
I even work at an Apple repair shop for service credibility (and certified, though Apple really sucks, it's still a tech job.)
Honestly, I just dont like that it isnt working....
I have real use for it, just wanted to get it working to play with it. Its in REALLY poor condition. It was stolen from me twice and the second time it was damaged but still operational. I am pretty sure what I need to recover it is the final 2.95.651.6 from Sprint that isn't anywhere I can find online and as you said, customer service isnt very....helpful....
Now I saw the ruu unpacking thread and I wonder if a ruu could be built with the correct version all
with it locked and s-on any ruu will have to be signed by htc to install.
I'm fresh out of ideas. since all my 3vos but the one I just got are virgin mobile branded, most of my stored files are for that, the only sprint ruu files I've found yet are in the Android forums link.
and I didn't look very hard, since mine went s-off super easy on the very first tickle with the wire trick and I can install any ruu I want.
if you're desperate enough, maybe taking it s-off would allow you to flash an older ruu. if it'll s-off in its current condition. it's supposed to be unlocked for that and on stock rom.
the unlimited.io pages for the wire trick are gone, but they live on through the Wayback Machine (Internet Archive) including download links.
did you try using the stock recovery which should be on yours and do a factory reset through there?
That's the error I get going into recovery and the results from that factory reset...
My stuff is never easy to fix lol if I'mma have an issue it's gonna be complicated ?
can you get a picture of the hboot screen?
It's from fastboot menu but the tops the same
one more thing, can you
fastboot getvar all
I hate to give up on something like this where it's only soft bricked. still boots to the bootloader, and still has fastboot.
it clearly didn't unlock though, like you said.
also a thought:
have you tried retrieving the
fastboot oem get_identifier_token
again and getting a fresh download of the unlock token from htc? maybe the one you have got corrupted.
and since you're dealing with Micro$oft, you might have to uninstall all the htc drivers and install the htc sync program for the 3d to get the correct one. it sounds like you've been playing with a lot of modifications.
ubuntu live cd might be worth a try, there's no nonsense about device drivers in ubuntu for android phones.
I have gotten the unlock token 6 times now I've tried from win7 and win10, Kali Linux, FWUL, and from android to android (I have adb on my essential) I can try Ubuntu live though, won't hurt to try....
I was looking for a good copy of the urt HTC recovery bootable but no luck
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.58.0000
(bootloader) version-baseband: 1.09.00.0108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.95.651.6
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) product: shooter
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3f645641
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s