Database Develop

[Q] Can't unlock HTC One GPE that is RELOCKED

I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86

Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.

Arjen_Arg said:
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Click to expand...
Click to collapse
From what I've been able to determine I'm unable to achieve S-OFF with HBOOT 1.54, or else I definitely would.

There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
msw141 said:
I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Click to expand...
Click to collapse

That's old information. There has been an S-Off exploit for 1.54 for over a month. I've done it on a GPE just like yours. Search for Rumrunner S-Off.
---------- Post added at 07:43 PM ---------- Previous post was at 07:35 PM ----------
ipfreelytech said:
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
This is wrong. You CAN S-OFF a GPE. Although you need root access or unlocked bootloader.
Do you have root?
Rumrunner S-Off http://rumrunner.us/

edit. answered in post above

ipfreelytech said:
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s

Arjen_Arg said:
Do you have root?
Click to expand...
Click to collapse
No root, sadly. And probably can't get it with locked bootloader and s-on either.

interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
msw141 said:
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Click to expand...
Click to collapse

ipfreelytech said:
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Well the firmware flash worked just fine. But then I tried flashboot oem unlock and I got the same error as documented earlier. I even tried the HTCdev method again, got a successful result but no unlock screen.
So I'm still stuck on relocked. But I'm encouraged that your file was able to flash with no error. Do you think there might be more files I could attempt to flash in that manner that could help?

ipfreelytech said:
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?

SaHiLzZ said:
Hi,
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
When I first got my phone I unlocked via that HTCdev method by betting the unlock_code.bin file and flashing it. I wasn't aware until today that there was a different method for GPE that didn't require that. The problem now is that the oem unlock doesn't work, and HTCdev method says it works but doesn't complete.

Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.

SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
OK, understood. What do you suggest I keep an eye out for on the forums?
A new S-OFF method for 1.54 with a locked bootloader...a new firmware update where it might work again...or updated drivers for the hardware/adb? Appreciate your input.

adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if you're s off and have root
SaHiLzZ said:
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse

Ah Ok, that is what Guru's bootloader zip is based on. Thanks!

ipfreelytech said:
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if your s off and have root
Click to expand...
Click to collapse
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....

doubtful. s-off is required because your modifying a "black box" partition. The solutions used to gain s-off in the first place require using an exploit to write to that partition. What i posted is just directly modifying it using dd.
elisaw99 said:
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
Click to expand...
Click to collapse

SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.

msw141 said:
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
Click to expand...
Click to collapse
Im getting this same issue after updating to 4.4.2 after i got my phone back from repair. It is completely stock now and when i try to unlock the phone it wont show the screen that asks me if im sure i want to unlock my phone, which is the last step on the htcdev site.
Im thinking its a kitkat issue.

[Q] Recommend appropriate RUU to install stock ROM for HTC One

Hello,
I'm using HTC One which was initially locked by 3 network (UK) and i got it unlocked last month. I have unlocked my boot-loader and rooted my phone recently. My phone got updated to android version 4.3, after the upgrade i tried performing S-OFF using REVONE but i was not able to S-OFF my device. To install a custom ROM i have to be S-OFF. I have to revert back to stock android version. Could anybody please suggest me which version of RUU should i use to install stock ROM to my device?
I have HBOOT version 1.55.0000
I don't know what is it but when i start my device in boot-loader mode these are all the information i could find:
M7_UL PVT SHIP S-ON RH
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
I have relocked my device and all set to revert back to stock android version. please help me to find correct version of RUU to use for my device. I'm totally new to all these ROM stuffs and if i have mentioned some technical terms wrong my apologize guys.
Thanks in advance.

rprx134 said:
Hello,
I'm using HTC One which was initially locked by 3 network (UK) and i got it unlocked last month. I have unlocked my boot-loader and rooted my phone recently. My phone got updated to android version 4.3, after the upgrade i tried performing S-OFF using REVONE but i was not able to S-OFF my device. To install a custom ROM i have to be S-OFF. I have to revert back to stock android version. Could anybody please suggest me which version of RUU should i use to install stock ROM to my device?
I have HBOOT version 1.55.0000
I don't know what is it but when i start my device in boot-loader mode these are all the information i could find:
M7_UL PVT SHIP S-ON RH
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
I have relocked my device and all set to revert back to stock android version. please help me to find correct version of RUU to use for my device. I'm totally new to all these ROM stuffs and if i have mentioned some technical terms wrong my apologize guys.
Thanks in advance.
Click to expand...
Click to collapse
1- relocking was not the wisest decision, better unlock again
2- to install custom rom, you only need unlocked bootloader and custom recovery. S-Off is NOT needed
3- to get s-off on hboot 1.55, use http://rumrunner.us/ (with compatible ROM, I think ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023)

Android 4.4 rom Installation in HTC One.
nkk71 said:
1- relocking was not the wisest decision, better unlock again
2- to install custom rom, you only need unlocked bootloader and custom recovery. S-Off is NOT needed
3- to get s-off on hboot 1.55, use http://rumrunner.us/ (with compatible ROM, I think ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023)
Click to expand...
Click to collapse
Thanks a lot for your help, and i did S-OFF for my device. If you don't mind please help me with this issue i tried installing android kitkat 4.4 rom for my HTC One using clockworkMod recovery but i ended up getting some error and my installation was aborted. The error is like this "Warning - No Context found". Please help me to figure out the problem.
Thanks.

rprx134 said:
Thanks a lot for your help, and i did S-OFF for my device. If you don't mind please help me with this issue i tried installing android kitkat 4.4 rom for my HTC One using clockworkMod recovery but i ended up getting some error and my installation was aborted. The error is like this "Warning - No Context found". Please help me to figure out the problem.
Thanks.
Click to expand...
Click to collapse
use latest TWRP (2.6.3.3 or above), i believe CWM hasn't been updated for 4.4 ROMs yet: http://forum.xda-developers.com/showthread.php?t=2173870
verify MD5 of twrp before flashing!!

TWRP should work, maybe need to format. I always use the HTC One Developer Edition RUU zip that can be found on HTC Dev site as well as the numerous threads around XDA.

roryrjb said:
TWRP should work, maybe need to format. I always use the HTC One Developer Edition RUU zip that can be found on HTC Dev site as well as the numerous threads around XDA.
Click to expand...
Click to collapse
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.

for righuen
st.zapto said:
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.
Click to expand...
Click to collapse
Hello, I meant i unlocked my device in a boutique. I don't think we can do that our-self. Thanks.

st.zapto said:
Hi there, how did you managed to unlock your network lock? (SIM lock). I rooted it and writes down a revolution hd rom but it still has a SIM lock... Thanks for any help here or in private.
Click to expand...
Click to collapse
Actually I haven't tried a different SIM, but I'm sure it would work.

[Q] Ran RUU - Now have S-OFF w\Relocked Bootloader

Would appreciate some advice before I move forward ....
I was running ViperOne 4.2.0 happily, albeit on a very old firmware version.
However on trying to flash a current firmware it failed with "FAILED (status read failed (too many links))" which left me stuck with the silver HTC on a black screen with the 4 warning triangles in each corner.
I then downloaded and flashed this: "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed" which got me back up and running ......
However, my current bootloader info is:
*** RELOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,20:01:03:-1
What steps do I need to take to get back to root, with custom recovery, latest firmware and be able to flash ViperOne again?

channelsurfer99 said:
Would appreciate some advice before I move forward ....
I was running ViperOne 4.2.0 happily, albeit on a very old firmware version.
However on trying to flash a current firmware it failed with "FAILED (status read failed (too many links))" which left me stuck with the silver HTC on a black screen with the 4 warning triangles in each corner.
I then downloaded and flashed this: "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed" which got me back up and running ......
However, my current bootloader info is:
*** RELOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,20:01:03:-1
What steps do I need to take to get back to root, with custom recovery, latest firmware and be able to flash ViperOne again?
Click to expand...
Click to collapse
So you've done an RUU , and it got stuck in the RUU screen?
Try "fastboot oem restart*
Then boot intro bootloader.
Download CMW/TWRP
then flash the recovery
Turn Adb-sideload on in recovery, use adb sideload to install ViperRom again.

Unlock using "revone -u"
Sent from my HTC One using Tapatalk

Gixy said:
So you've done an RUU , and it got stuck in the RUU screen?
Try "fastboot oem restart*
Then boot intro bootloader.
Download CMW/TWRP
then flash the recovery
Turn Adb-sideload on in recovery, use adb sideload to install ViperRom again.
Click to expand...
Click to collapse
No, the RUU finshed fine and it rebooted back into the stock ROM with stock recovery, however when I try to flash recovery (twrp 2.6.3.3) it fails with:
"FAILED (remote: not allowed)"
Is this due to the bootloader being "Relocked"? If so, any idea how to Unlock it again .... I used HTC Dev to initially unlock it way back when and rumrunners to get S-OFF
Thanks for the help!

You can do what nkk71 has suggested or unlock using htcdev by generating a new unlock key.

nkk71 said:
Unlock using "revone -u"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
nkk, as I didn't use Revone to get S-OFF, would that still be a valid way of getting back to Unlocked, do you think?

Unlock using HTC dev? revone is for 1.44 hboot

SaHiLzZ said:
Unlock using HTC dev? revone is for 1.44 hboot
Click to expand...
Click to collapse
SuperCID, dont think that HTCdev has an unlock token for that
---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------
channelsurfer99 said:
nkk, as I didn't use Revone to get S-OFF, would that still be a valid way of getting back to Unlocked, do you think?
Click to expand...
Click to collapse
revone -u
has nothing to do with s-off, it's just unlocking using; eg: http://forum.xda-developers.com/showthread.php?t=2475914

He ran the RUU zip. that assumes that phone is not rooted anymore.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
Click to expand...
Click to collapse

revone has m/'
Revone had m/c exploit!
Sent from my HTC One using Tapatalk
---------- Post added at 12:08 AM ---------- Previous post was at 12:08 AM ----------
nkk71 said:
revone has
Revone had m/c exploit!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk

channelsurfer99 said:
No, the RUU finshed fine and it rebooted back into the stock ROM with stock recovery, however when I try to flash recovery (twrp 2.6.3.3) it fails with:
"FAILED (remote: not allowed)"
Is this due to the bootloader being "Relocked"? If so, any idea how to Unlock it again .... I used HTC Dev to initially unlock it way back when and rumrunners to get S-OFF
Thanks for the help!
Click to expand...
Click to collapse
When you run an RUU, i assume your bootloader has been locked, so if RUU is succesfull, your bootloader is currently locked/relocked.
Go to the HTC dev email you´ve received with the Unlock_code.bin . but this in your folder with adb & fastboot. Go into fastboot mode, and execute : ¨fastboot flash unlocktoken Unlock_code.bin¨
If you havn´t got this email anymore, go to the htcdev website and request your unlock code again as you did unlocking.
Then install TWRP/CMW, flash youŕe preffered rom
EDIT: Just read the other posts, use revone as
nkk71 suggested. Otherwise read up on the revone thread :
http://forum.xda-developers.com/showthread.php?t=2314582

As suggested, I used my original HTC Dev token to successfully unlock the bootloader from it's "Relocked" state.
Then I was able to flash TWRP and reflash ViperOne ... So I'm back to where I started from thankfully!
The only problem I'm having is getting the right PC drivers installed to connect the phone to transfer files ...... That's going to have to wait until tomorrow now as it's late here!
Thanks to everyone for the help and advice

Need help with S-Off/which rom?

Hi,
I've not flashed my phone for what feels like years (I think it was start of 2014). I see most of ROMs require S-OFF, but I'm not having much luck with that.
TWRP installed
Rooted
CyanogenMod 10.2.1-myul
4.3.1
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4a.13.3231.27
OpenDSP-V26.120.274.0202
Emmc-BOOT
Mar 7 2013,20:01:03-2
I get errors when trying to use either revone/rumrunner:
Revone error:
revone failed (error code = -1)
Rumrummer error:
After it reboots for a second time, it throws up an error
Can anybody point in the right direction? I was going to flash this RUU file...but thought I should check before going and bricking my phone (I from the UK and use the EE provider)
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Thank in advance (also, since I've been out of the game for a while...anything else that you think is a must would be appreciated!)

fracmo2000 said:
Hi,
I've not flashed my phone for what feels like years (I think it was start of 2014). I see most of ROMs require S-OFF, but I'm not having much luck with that.
Click to expand...
Click to collapse
Most of rom doesn't require s-off, only a few like GPE roms or Oneplus.
Code:
TWRP installed
Rooted
CyanogenMod 10.2.1-myul
4.3.1
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4a.13.3231.27
OpenDSP-V26.120.274.0202
Emmc-BOOT
Mar 7 2013,20:01:03-2
I get errors when trying to use either revone/rumrunner:
Revone error:
revone failed (error code = -1)
Rumrummer error:
After it reboots for a second time, it throws up an error
You must have root and unsecured kernel. Try with ARHD 31.6

alray said:
You must have root and unsecured kernel. Try with ARHD 31.6
Click to expand...
Click to collapse
I should of said, Im not a fan of sense roms (I wanted to try a GE rom haha). So, just to clarify, I flash
http://forum.xda-developers.com/showthread.php?t=2183023
Could I then flash another rom ontop (would this fix my hboot version or whatever is causing the problems just now?).
I have everything backed up with Titanium Backup, just wanted to double check (downloading it as I type!)
ALso, thanks so much for reply...i've tried for two days straight...I knew you guys would have the answer

fracmo2000 said:
Could I then flash another rom ontop
Click to expand...
Click to collapse
you can always flash another rom
(would this fix my hboot version or whatever is causing the problems just now?)
Click to expand...
Click to collapse
Flashing a rom will not change hboot version. To use revone, you must have root access, an unsecured kernel and a rom that match your firmware version. Thats why I suggested you to flash ARHD 31.6. Then try revone again.

alray said:
you can always flash another rom
Flashing a rom will not change hboot version. To use revone, you must have root access, an unsecured kernel and a rom that match your firmware version. Thats why I suggested you to flash ARHD 31.6. Then try revone again.
Click to expand...
Click to collapse
Ah ok, i get you now. I've finished work but will re-try tomorrow and report back. Thanks man

Edit: It started to go horribly wrong, but managed to get it working. It seems the ARHD and others were not being copied over properly when using the sideload feature in the All-In-One toolkit. It kept saying
sending 'sideload' 100%
but when checking the phone it says "ADB Sideload Complete FAILED"
I tried various roms and got the same error. Weird. Ended up trying
Slim rom (under 1gb) and it worked a treat
http://forum.xda-developers.com/showthread.php?t=2590642

htc one m7 stuck at recovery mode with HBOOT: 1.61

M7 stuck in recvery mode in twrp mode, let me know the solution and the info of phone is given below
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T . 35. 3218. 16
OpenDSP-V35. 120. 274. 0718
OS-7. 21. 707. 105
eMMC-boot 2048MB
Mar 12 2015, 17:04:43.0
please guide me how to flash it or how to recover it, i will be highly oblidge to you

1. set ur botloader to relock
2. change ur cid to original
3. start RUU match with ur CID

deadcore said:
1. set ur botloader to relock
2. change ur cid to original
3. start RUU match with ur CID
Click to expand...
Click to collapse
could be you please explain it with link so that i can download file from link that you will provide and do the same as you says

mandeepsgh1 said:
M7 stuck in recvery mode in twrp mode, let me know the solution and the info of phone is given below
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T . 35. 3218. 16
OpenDSP-V35. 120. 274. 0718
OS-7. 21. 707. 105
eMMC-boot 2048MB
Mar 12 2015, 17:04:43.0
please guide me how to flash it or how to recover it, i will be highly oblidge to you
Click to expand...
Click to collapse
mandeepsgh1 said:
could be you please explain it with link so that i can download file from link that you will provide and do the same as you says
Click to expand...
Click to collapse
Either 7.21.707.105 or 7.21.707.121 will work. Check the sticky threads in the general section, You'll find a ruu collection thread with files + instructions.

alray said:
Either 7.21.707.105 or 7.21.707.121 will work. Check the sticky threads in the general section, You'll find a ruu collection thread with files + instructions.
Click to expand...
Click to collapse
as i searched on internet , there is a need of S-OFF to flash RUU file.
but there is S-ON on my htc one.
& i dont know how to make it S-OFF.
Please guide me for the same.
my bootloader is unlocked, but when i tried to put rom from "adb sideload abcs.zip" it show cannot read sideload.
and when i tried to select the rom from sdcard(internal storage) then it was at the end as set_metadata_changes_failed
i think this is due to S_ON.
please guide me to make it S-OFF

mandeepsgh1 said:
as i searched on internet , there is a need of S-OFF to flash RUU file.
but there is S-ON on my htc one.
& i dont know how to make it S-OFF.
Please guide me for the same.
Click to expand...
Click to collapse
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
my bootloader is unlocked
Click to expand...
Click to collapse
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
but when i tried to put rom from "adb sideload abcs.zip" it show cannot read sideload.
and when i tried to select the rom from sdcard(internal storage) then it was at the end as set_metadata_changes_failed
i think this is due to S_ON.
please guide me to make it S-OFF
Click to expand...
Click to collapse
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.

alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
i tried with RUU version 7.21.707.121 , but when i tried to flash it by fastboot , it gives an error, " cannot allocate ROM.zip"
please guide me for stock or to put any custom ROM so that i can use my phone, it is being 5 days without my htc one.
please help

alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
when i try to relock my htc one m7, with , "fastboot oem lock"
it shows me this:
(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.239s
here, second last line show failed but on bootloader it shows me RELOCK
Is it going good or there is any issue???

alray said:
You don't need s-off to flash a RUU, read the instructions of the RUU collection thread. S-OFF is only needed when you want to use a RUU to downgrade your phone or to convert to another carrier version. If flashing the same or newer version like 7.21.707.105 or 7.21.707.121, you don't need s-off.
With s-on, you must re-lock the bootloader to flash a ruu, like said in the instructions.
Are you taking about the RUU here? Or another rom you did not mentioned before? If you are talking about the RUU, it can't be flashed using a recovery, only using fastboot (read the instructions). If you are talking about a custom rom then it smost likely because you are using an outdated adb version or an outdated recovery version or a combination of both.
Click to expand...
Click to collapse
thank you so much sir, today i tried with ruu 7.21.707.105, it is being successful believe me xda & you come as an "angel engineer". but thee is only one query from my side, is there any issue with tempered or relocked bootloader??