@nkk71
I have been scouring the internet for weeks, and trying many different thing to try and resolve my issue, but to no avail.
I thought I would start again..... Completely!
I live in the UK, I bought and HTC One from Three (Sense Edition), upon using this phone for a month, i grew tired of the uninteresting interface and lack of vigour. So i decided to convert it, to 4.4.
All went well for a while, then I decided I wanted to do a full conversion and get the Google Edition OTA updates. so here is my predicament.
I unlocked my bootloader from HTCDev originally, and only S-off'd my phone for the conversion.
Code:
(bootloader) version: 0.5
[COLOR="Red"][B](bootloader) version-bootloader: 1.54.0000[/B][/COLOR]
[COLOR="red"][B](bootloader) version-baseband: 4T.21.3218.21[/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
[COLOR="Red"][B](bootloader) version-main: 3.58.1700.5[/B][/COLOR]
[COLOR="red"][B](bootloader) version-misc: PVT SHIP S-ON[/B][/COLOR]
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
[COLOR="red"][B](bootloader) modelid: PN0710000[/B][/COLOR]
[COLOR="red"][B](bootloader) cidnum: GOOGL001[/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4198mV
(bootloader) partition-layout: Generic
[COLOR="red"][B](bootloader) security: on[/B][/COLOR]
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now. I S-offed, and fully RUU flashed the 4.3 Google Play Edition RUU from the HTC1Guru.
Upon completion I sreset S-on using
Code:
fastboot oem writesecureflag 3
and finished with
Code:
fastboot oem lock
ok So i guess its not all that bad, I have a working phone with OTA updates, as it updated to 4.4 with no problems at all, However... I play around with my phone quite a bit and decided i want to make a backup of my phone so I can try a new ROM.
At first I tried to unlock my HTC One again with HTCDev - and after googling why it didn't work i felt like an idiot.
so i used
Code:
fastboot oem unlock
to receive the following
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.531s]
finished. total time: 0.531s
I cannot unlock, I cannot S-Off, I cannot flash RUUs because i get either
Code:
Main-Version check failed or Signature Verification Failed
All I want to do is unlock the bootloader, and I cannot seem to do so. I defer to the experts here and hope you would impart some wisdom on me
Me Too。。。。。。。。。。
Related
Hi guys,
My phone bricked after I rooted my htc one 801e and attempted to install busybox. When I entered twrp recovery, most of the actions I did resulted in "unable to mount system"
Browsing around online, I came across some guides to restore stock ruu. i went and fastbot oem locked my phone and now I'm stuck. Lost recovery, (any attempt to access recovery only resulted in returning to fastboot menu) re-flashing recovery and/or ruu results in "FAILED (remote: 12 signature verify fail)"
Does anyone have any solution(s) to this?
my info is as follows:-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxcxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: xxxxxxxxx
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2a2b2444da
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
You need to unlock bootloader. What RUU you tried? Sounds like it was not official.
SaHiLzZ said:
You need to unlock bootloader. What RUU you tried? Sounds like it was not official.
Click to expand...
Click to collapse
I tried to re-unlock bootloader but it doesnt work. Gave me signature error. as for the ruu, i tried both http: //www .androidruu .com/index.php?developer=M7 and Guru Reset versions. Both gave signature errors. Basically, trying anything seems to give signature error. Hence I cant install recovery nor can I unlock bootloader.
I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?
badgcoupe said:
I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?
Click to expand...
Click to collapse
Do you have stock or custom recovery installed?
I had TWRP installed but now it will not boot to it via the recovery option in hboot, it just goes back into the loading google boot loop. I just tried to repush TWRP to the device but got FAILED (remote: signature verify fail)
Brought the phone to ATT and they actually gave me another one. Lesson learned.
HI,
I've converted my HTC one into a google play edition, but this morning i wanted to convert it back to stock HTC rom and I guess I messed it all up.
Whenever I turn my phone one it loads into android but then reboots after a second or two. The only way to stop this loop is to press power and volume down and enter the bootloader. From here I can shut down the phone. I'm not able to do a recovery or a factory reset.
The phone says tampered and relocked. My question is how to unlock it again? the htcdev method don't seem to be working neither does the fastboot oem unlock command.
fastboot getvar all gives me the following:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4173mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
the fastboot oem unlock commands returns the following:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.538s]
finished. total time: 0.539s
I've searched high and low but without much luck. Hope someone is able to help me out!
Hey guys,
I'm usually not too bad at this, but after many attempts, I could not return back to the TMOBILE stock 5.0.2 for my M7.
My first attempt:
Run the RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421697_signed_2.exe, when it boots into fastboot and RUU mode, htc_fastboot.exe crashes and stops working. I have attached a picture of the firmware upgrade screen.
Second attempt:
Download the ruu zip from http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 for tmobile US, ran htc_fastboot oem rebootRUU, htc_fastboot flash zip ruu.zip
Code:
C:\Users\Alen\Desktop>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 0
OKAY
Execution time is 35(ms)
C:\Users\Alen\Desktop>htc_fastboot flash zip RUU.zip
sending 'zip'... (43290 KB) OKAY
sending time = 3.105 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 4(s)
C:\Users\Alen\Desktop>
Here is the var dump for my phone:
Code:
C:\Users\Alen\Desktop>f getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 67(ms)
I tired this multiple times, but don't know whats up. I'm doing this S-OFF with the bootloader unlocked.
I'd appreciate any help, as i'm shipping my phone back to HTC.
Akeid said:
Hey guys,
I'm usually not too bad at this, but after many attempts, I could not return back to the TMOBILE stock 5.0.2 for my M7.
My first attempt:
Run the RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421697_signed_2.exe, when it boots into fastboot and RUU mode, htc_fastboot.exe crashes and stops working. I have attached a picture of the firmware upgrade screen.
Second attempt:
Download the ruu zip from http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 for tmobile US, ran htc_fastboot oem rebootRUU, htc_fastboot flash zip ruu.zip
Code:
C:\Users\Alen\Desktop>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 0
OKAY
Execution time is 35(ms)
C:\Users\Alen\Desktop>htc_fastboot flash zip RUU.zip
sending 'zip'... (43290 KB) OKAY
sending time = 3.105 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 4(s)
C:\Users\Alen\Desktop>
Here is the var dump for my phone:
Code:
C:\Users\Alen\Desktop>f getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 67(ms)
I tired this multiple times, but don't know whats up. I'm doing this S-OFF with the bootloader unlocked.
I'd appreciate any help, as i'm shipping my phone back to HTC.
Click to expand...
Click to collapse
In addition to having the correct CID and MID, 7.xx.531.x RUU needs 2 things to be flashed:
hboot version must be at least 1.57
firmware version must be at least 6.xx.531.x
So flash the firmware first, if you can't find it then flash an older RUU.zip (Downgrade)
Is there any way i can RUU so that the hboot stays at 1.54 or 1.55 so i can s-off in the future?
Akeid said:
Is there any way i can RUU so that the hboot stays at 1.54 or 1.55 so i can s-off in the future?
Click to expand...
Click to collapse
you already have s-off
alray said:
you already have s-off
Click to expand...
Click to collapse
I'm on tmobile stock rom from the RUU after upgrading my FW, but now I am wondering, since my device is on hboot 1.61 and i am about to lock the boot loader and S-ON, when my phone gets back form the factory, will i be able to s-off on the new hboot.
here's my current getvar:
Code:
C:\Users\Alen\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4224mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.111s
C:\Users\Alen\Desktop>
Thanks for the help buddy.
You can go all the way back to 1.44 hboot, and s-on there, so you can soff using revone when it comes back. Then send it over for warranty. However if they change the motherboard, you may not get back the same firmware level
Akeid said:
I'm on tmobile stock rom from the RUU after upgrading my FW, but now I am wondering, since my device is on hboot 1.61 and i am about to lock the boot loader and S-ON, when my phone gets back form the factory, will i be able to s-off on the new hboot.
here's my current getvar:
Code:
C:\Users\Alen\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4224mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.111s
C:\Users\Alen\Desktop>
Thanks for the help buddy.
Click to expand...
Click to collapse
You should know that currently you are not on T-Mobile firmware, you are on wwe world wide English, and although your mid and cod say your on T-Mobile, your version main says your on wwe 401 not 531, if you send it back like that, they will know for sure that you messed with it, locked and a-on or not.
Thanks for all the help! I ended up flashing the 3.24.531.3 fw via fastboot, then flashing the 3.24.531.3 RUU.zip. I'm S-on now with no tamper and locked boot loader. Hboot 1.55 is able to be s-off'ed, so just in case they send me back the phone with only a replaced camera module and the same motherboard, I will be able to s-off again.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4299mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hi all,
Have this phone, GPE, unmodified, but running 5.1 (Not 4.4)
fastboot get vars gives:-
Code:
(bootloader) version: 0.5
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36********
(bootloader) imei: 35**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
fastboot oem unlock gives:-
Code:
$ sudo fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.274s]
finished. total time: 0.274s
Trying the HTCdev unlock path also fails, the code is written to the device, sure, but it never creates the unlock splash confirmation screen.
Kind of at my wit's end with this device at this point - I've seen threads here (from 2014) regarding this, but nothing much in the period since.
Any ideas on where I should go with this?
khavakoz said:
Hi all,
Have this phone, GPE, unmodified, but running 5.1 (Not 4.4)
fastboot get vars gives:-
Code:
(bootloader) version: 0.5
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36********
(bootloader) imei: 35**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
fastboot oem unlock gives:-
Code:
$ sudo fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.274s]
finished. total time: 0.274s
Trying the HTCdev unlock path also fails, the code is written to the device, sure, but it never creates the unlock splash confirmation screen.
Kind of at my wit's end with this device at this point - I've seen threads here (from 2014) regarding this, but nothing much in the period since.
Any ideas on where I should go with this?
Click to expand...
Click to collapse
If I remember correctly, this problem affected all GPE m7 since 2014 when they pushed the 4.4.2 OTA update. They never (Google or neither HTC) solved this in later updates.
If you really want it to be unlocked, you could try to achieve S-OFF with the same method used for the Verizon variant. Once S-OFF achieved you can flash and boot TWRP recovery even if the bootloader is locked. Boot the recovery and unlock the bootloader using TWRP command terminal
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
https://forum.xda-developers.com/ve...root-root-method-bl-unlock-5-0-x-ota-t3122099