Database Develop

[Q] Help! Phone bricked, TWRP won't start :(

I upgraded the firmware on the HTC One (AT&T Branded). In order to do that, I had to relock the bootloader and flash firmware.zip using fastboot. I did have a proper Nandroid backup from TWRP before doing this.. Now the phone is bricked, and TWRP does not start for some reason...
I can't flash TWRP again because the bootloaded is relocked.. And when I request the bootloader unlock key from htcdev.com, I get an error
Error Code: 173.
Error Reason: Check Rule Fail with exception.
Is there any way I can get around this?

Quick update - @HTCDev came back and told me that their unlock service was down. They fixed it now and I was able to download the unlock code file.
HOWEVER, when I go to fastboot and try to flash it, nothing happens on the device (the status still shows relocked) even though fastboot says that the command succeeded..
C:\Users\walletless\Desktop\One_All-In-One_Kit_v\Data>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.167s
I also tried "fastboot reboot-bootloader" after this and it still shows status as relocked. I am on hboot 1.56 and supercid if it matters.
Anyone has suggestions?

fastboot getvar all shows:
Code:
(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-OFF
(bootloader) serialno: (delete)
(bootloader) imei: (delete)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4259mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.095s

Also tried fastboot erase cache.. Command completed successfully but still cannot boot into recovery
Next try would be ruu... any idea which RUU I should try?
I cant use guru reset since booting into recovery does not work (I get a screen with a red triangle and exclamation when I attempt to boot to recovery)

Finally, found a solution. Phew!
Just flashed an older firmware (http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip) and I am able to boot into android now...

You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.

farang4u said:
You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.
Click to expand...
Click to collapse
I cant reflash anything for some reason.. the bootloader remains in "relocked" state even after I flash unlockcode..
Immediately after flashing unlockcode, my command window shows:
Code:
> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.165s
And the phone freezes on the fastboot screen - does not respond to any button presses, etc..

Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!

walletless said:
Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!
Click to expand...
Click to collapse
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.

gunswordx said:
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.
Click to expand...
Click to collapse
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app

walletless said:
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
gpe is the google edition firmware not having sense

gunswordx said:
gpe is the google edition firmware not having sense
Click to expand...
Click to collapse
Ah ok, that I did not try. Thanks for the tip!
Anyway, phone is up and running well now.. Rocking Android RevolutionHD 40.2

[Q] Tampered, Unlcoked, S-On Hboot 1.57 - No USB Debug Semi Bricked

Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
C:\AndroidSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXX
(bootloader) imei:XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse

PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
Click to expand...
Click to collapse
You must flash ARHD using TWRP 2.6.3.3
you can not use older RUU version to restore your phone with S-ON
You can restore your phone back to stock using a nandroid backup of your version and then flash the stock recovery back.
USB debugging is only needed to use ADB when the phone is booted in the OS. Or you can also use ADB from custom recovery even if USB debug is NOT turned on.
So depending what your goal is you should try to either flash TWRP 2.6.3.3 and reflash ARHD or restore your phone using a nandroid backup if the latest dev edition software.

PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
Click to expand...
Click to collapse
alray is correct, you can not flash that RUU because you are S-ON and it is a lower version than your present phone. There is no RUU for your version at the moment only an OTA. Here is the stock firmware for your version. This would give you stock recovery, stock hboot but it may wipe all of your personal data off of the phone. Place the file in your fastboot/adb folder and rename it firmware.zip. Then you would flash it in bootloader/FASTBOOT USB:
Code:
[B][I]fastboot oem lock[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
After the reboot, you can install TWRP and then flash ARHD 81.0.

C:\AndroidSDK\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.146s
C:\AndroidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.034s]
finished. total time: 0.034s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.657s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.713s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.709s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.710s
C:\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
I downloaded the file and flashed it, that's what I got.

I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.

PlinXoom said:
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
Click to expand...
Click to collapse
Achieve S-OFF with firewater or sunshine
Download and install this Bootloader Reset Tool

I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?

PlinXoom said:
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
Click to expand...
Click to collapse
If you develop an issue down the road it is easier to fix with the phone being S-OFF. However, it is a personal choice.

I figured as much, thanks again! :highfive:

Help flashing firmware.

I have been trying to update a firmware to I can run the new lp rom. It says the new firmware is required. His phone is s-on and I used the new twrp..
E:\greg\lollipop>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.150s
E:\greg\lollipop>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3

budeone said:
I have been trying to update a firmware to I can run the new lp rom. It says the new firmware is required. His phone is s-on and I used the new twrp..
E:\greg\lollipop>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.150s
E:\greg\lollipop>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
Click to expand...
Click to collapse
Is there a question in there somewhere?

BD619 said:
Is there a question in there somewhere?
Click to expand...
Click to collapse
ROFLMAO
Yeah.. sorry.. it keeps failing.. I have tried to do a RUU after locking it back up.. I have tried everything I can think of.. just wont let me update.

budeone said:
ROFLMAO
Yeah.. sorry.. it keeps failing.. I have tried to do a RUU after locking it back up.. I have tried everything I can think of.. just wont let me update.
Click to expand...
Click to collapse
What errors are you getting?

BD619 said:
What errors are you getting?
Click to expand...
Click to collapse
FAILED (status read failed (Too many links))

budeone said:
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
You got that error when you re-locked right?
If so that's normal...does bootloader say RELOCKED?

BD619 said:
You got that error when you re-locked right?
If so that's normal...does bootloader say RELOCKED?
Click to expand...
Click to collapse
I relocked and get that message. Nothing changed in the phone I am still on the 1.0 version of firmware. Then I have no recovery unless I unlock again. I am starting to wounder if I cant go from the very first firmware to the latest?

budeone said:
I relocked and get that message. Nothing changed in the phone I am still on the 1.0 version of firmware. Then I have no recovery unless I unlock again. I am starting to wounder if I cant go from the very first firmware to the latest?
Click to expand...
Click to collapse
In theory you should be able to go right to the latest.

BD619 said:
In theory you should be able to go right to the latest.
Click to expand...
Click to collapse
I know if I were s-off I would not be having these issues. I am not paying $25.00 bucks for someone else phone.

Todd what's up when did you get an m8?

FrozenRiff said:
Todd what's up when did you get an m8?
Click to expand...
Click to collapse
Its my boss's phone. I have tried everything and I cant get it to work.. I even tried buying him shunshine and that wont work.

[Q] EU GSM return to stock rom (want official L)

Hi, i was searching forums but i never find out how to return to stock rom so i can have stock lollipop. I found guide (htc1guru) but it's outdated a bit and fastboot stopped working when sending RUU sign to phone.
SO, here are questions:
Is it possible?
How can i return to stock?
what file should i flash or idk?
getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.29.3218.08
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.09.401.10
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__032
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse

lapeno022 said:
Hi, i was searching forums but i never find out how to return to stock rom so i can have stock lollipop. I found guide (htc1guru) but it's outdated a bit and fastboot stopped working when sending RUU sign to phone.
SO, here are questions:
Is it possible?
How can i return to stock?
what file should i flash or idk?
getvar all
Click to expand...
Click to collapse
if you need to return to stock for warranty, you'll first need to schieve s-off using sunshine and then follow nkk71's guid elinked in my signature.
IF you only want to be on stock lollipop (not for warranty purpose) you can flash the 7.19.401.2 ruu posted in the general section.

Flash stock odexed 6.09.401.12 rom from recovery, reboot to bootloader and flash 6.09.401.12 firmware (you'll need fastboot for that). After all that boot the phone and check for updates. Or you can do what alray posted earlier.
-. typewrited .-

Thanks for replies

alray said:
if you need to return to stock for warranty, you'll first need to schieve s-off using sunshine and then follow nkk71's guid elinked in my signature.
IF you only want to be on stock lollipop (not for warranty purpose) you can flash the 7.19.401.2 ruu posted in the general section.
Click to expand...
Click to collapse
ok, so when i flash the 7.19.401.2, what will it update? just system or all other partitions (hboot, radios etc..) with it?
all what i want to do is to flash viperone 8.0.0 but last try ended with bootloop (on first try, it reboots into recovery), or maybe try stock L.
also when i relock bootloader, will be possible to unlock it again?

lapeno022 said:
ok, so when i flash the 7.19.401.2, what will it update? just system or all other partitions (hboot, radios etc..) with it? It will update everything, it is the ROM Utility Update.
all what i want to do is to flash viperone 8.0.0 but last try ended with bootloop (on first try, it reboots into recovery), or maybe try stock L.
also when i relock bootloader, will be possible to unlock it again?
Click to expand...
Click to collapse
Yes, you should be able to unlock it again after the update.

okay, so i am stucked at flashing RUU.zip.
commands:
C:\Program Files (x86)\ADB>htc_fastboot oem lock
... (bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
Execution time is 1(s)
C:\Program Files (x86)\ADB>htc_fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.517 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 8(s)
Click to expand...
Click to collapse
+ in bootloader is showing now security warning...

lapeno022 said:
okay, so i am stucked at flashing RUU.zip.
commands:
+ in bootloader is showing now security warning...
Click to expand...
Click to collapse
Did you follow this sequence?
Code:
[B][I]htc_fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]htc_fastboot flash zip RUU.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]htc_fastboot flash zip RUU.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]htc_fastboot reboot[/I][/B]
Click to expand...
Click to collapse

majmoz said:
Did you follow this sequence?
Click to expand...
Click to collapse
oh, i miss oem rebootRUU
done, with viperone 8.0.0 )

Managed to soft-brick my HTC One m7, need help to recover

Hi everyone, I inherited a used HTC One m7 from my son after my iPhone 4 died. This is my first android device. The phone worked perfect with the stock OS, except the green tint issue after a factory pink tint camera fix. My son never had the time to address the issue, but I decided to try to fix the problem by replacing the awb_cal file. I'm not a Linux guy, so I started from scratch.
Unlocked, installed TWRP, rooted. Because of my inexperience with not only TWRP, but Linux, during the process I managed to wipe clean my HTC. I read lots of instructions to get back in business, but some of them caused more trouble than help. Now, I ended up with a nonfunctioning beautiful piece of technology.
This is where I'm now:
(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.17.661.52
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW911052
(bootloader) imei: 354439053805232
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.137s
Using Windows 7 Pro, have installed the fastboot/ADB drivers, installed HTC Sync Manager.
TWRP 3.0.2-0 installed, but not working, can't get into twrp recovery from fastboot-usb mode, it returns to fastboot-usb. In this mode fastboot recognizes the device in cmd. The only way to get ADB recognize my device is to go through the Unlock_code routine. The phone boots right into TWRP, but stops responding at the Running OpenRecoveryScript screen, "Updating partition details... done - Full SELinux support is present. - Running Recovery Commands - Formatting Cache using make_ext4fs... - Wiping data without wiping /data/media ... - Done. - Done processing script file". It hangs here, but now ADB recognizes my device. After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
I tried to flash the PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip file in Relocked, with htc_fastboot in rebootRUU mode, but after the first writing I cannot start the second flashing, because it doen't stop but starts sending 'zip' ... (43286 KB) by itself and gets unresponsive at that line:
sending 'zip'... (43286 KB) OKAY
sending time = 3.097 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT34RW9110
52...
sending 'zip'... (43286 KB)
Since that in the Bootloader it says in red: OS-7.17.661.52 (7.17.661.7)
I tried to give as much detail as I can, and now I need help please, what should I do. Thanks

vik919 said:
After rebooting manually into fastboot, it shows Tampered - Relocked, so the unlocking not finishing.
Click to expand...
Click to collapse
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).

alray said:
Unlocking the bootloader requires the stock recovery, not a custom recovery because when unlocking the bootloader, the phone must first make a factory reset using the stock recovery before the bootloader can be unlocked (this is to prevent unauthorized access to your data). If you don't have the stock recovery, your phone will try to boot it, custom recovery will boot instead of the stock one, unlock process will fail because the script is made for the stock recovery, phone will reboot to bootloader mode with the phone still in the locked/relocked state. Unfortunately, you can not boot custom software (recovery/rom/kernel) if the bootloader is locked/relocked. Flashing the recovery partition also requires an unlocked bootloader. You're kinda stock in an endless loop... You need to unlock the bootloader, bootloader unlock requires stock recovery, flashing back the stock recovery requires an unlocked bootloader... Long story short, never relock if custom software is installed.
When the phone is S-ON and (re)Locked, you can only flash signed files (official HTC files) that are same or newer version than what is already on your phone. You'll need to find either the 7.17.661.52 RUU or a 7.17.661.52 firmware.zip. (firmware.zip can be extracted from an ota update.zip so the 7.17.661.52 update file would be ok).
Click to expand...
Click to collapse
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?

vik919 said:
Thanks alray for your response.
So, that PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_ Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202 _signed.zip file can't flash somehow my 7.17.661.52 firmware? I was not able to find any other file for my phone then this one. I don't use the phone on the Telus network anymore. is there any workaround?
Click to expand...
Click to collapse
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs

alray said:
There is a 7.17.661.52 ruu on ir-file.com but downloading from this website requires a paid subscription
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip

vik919 said:
Is this the one you mean?
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.52_radio_4t.35.3218.16_10.33q.1718.01l_release_460209_signed.zip
Click to expand...
Click to collapse
Yes
Sent from my HTC One using XDA Labs

alray said:
Yes
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
I wouldn't mind to pay that 20 bucks if I knew that it would get me through the first steps to fix my phone. My only concern is that I already tried the
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip
file and it did not work. This is the one which went in once, but I didn't get the opportunity to flash second time. It is now hanging in brackets in my bootloader beside the 7.1.7.661.52 firmware number.
Also, I checked this file and I can't see any zip file in it I could extract. Wouldn't it be with that paid one which looks pretty much the same except the firmware version number?
PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.52_Radio_4T.35.3218.16_10.33Q.1718.01l_release_46020 9_signed.zip
Wait a minute!
I just double checked and found at IR-File.com under Firmware an other file for my phone.
pn07img_m7_ul_l50_sense60_mr_telus_wwe_7.17.661.7_radio_4t.35.3218.16_10.33q.1718.01l_release_420202_signed_hboot.zip
This file ending with _hboot.zip only 493.0 MB in size compare to the other two files which are both about 1.5 GB. Is it possible that this latter one has the firmware.zip in it I could extract?
Please, advise, which one do I need?