[Q] Can't unlock HTC One GPE that is RELOCKED - One (M7) Q&A, Help & Troubleshooting

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.

Related

[DEV][Solved]Need advanced help with HBOOT... Unique S-Off situation

Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Tilde88 said:
Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Click to expand...
Click to collapse
I thought once soff always soff I have ruu 2 times already after soff revone and was still able to flash the radio from the newest firmware. After every ruu it always said soff
Sent from my GT-P3113 using xda app-developers app
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
karn101 said:
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
Click to expand...
Click to collapse
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Tilde88 said:
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Click to expand...
Click to collapse
Oh, so you were more concerned that it said relocked than S-OFF. S-OFF was bolded so I thought you were saying "Uh oh" to the S-Off.

[Q] Re-locked, s-on, Security Warning, and cannot boot into Recovery. My options?

Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?

[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

[Q] How to update from 4.3 to 4.4?

Hello all,
I am new on this forum and i am total noob so I need Your help.
I have HTC One (m7). My phone was locked, and I send it to service to unlocked it to another network carrier. They unlocked it for me but recovery is now CWM 6.0.4.8. I want to update to 4.4 but OTA wont work. How to update to stock recovery and than update OTA? Or how to update with CWM? I found some tutorial on youtube how to change from cwm to twrp (because most of custom roms flash with twrp), but cmd saying some error. I only want 4.4 rom, stock or custom, it doesn't even matter to me. I read some threads but is just to complicated to me and I wont brick my phone. Thank You .
This is cmd error:
C:\Users\Intel\Desktop\recovery\platform-tools>fastboot devices
FA35LW909339 fastboot
C:\Users\Intel\Desktop\recovery\platform-tools>fastboot flash recovery openrecov
ery-twrp-2.7.0.0-m7.img
sending 'recovery' (9948 KB)...
OKAY [ 1.250s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.285s
C:\Users\Intel\Desktop\recovery\platform-tools>
What is your HBOOT version?
fastboot flash recovery openrecovvery works only on older HBOOTs (1.44 I think). You can flash a recovery by using the fastboot flash recovery recoveryname.img
Please refer to threads here: http://forum.xda-developers.com/showthread.php?t=2265618
or
http://forum.xda-developers.com/showthread.php?t=2173870
or
http://forum.xda-developers.com/showthread.php?t=2358738
BTW, if they unlocked the device for a different carrier, going back to stock will revert you the the original carrier before.
davebugyi said:
What is your HBOOT version?
fastboot flash recovery openrecovvery works only on older HBOOTs (1.44 I think). You can flash a recovery by using the fastboot flash recovery recoveryname.img
Please refer to threads here: http://forum.xda-developers.com/showthread.php?t=2265618
or
http://forum.xda-developers.com/showthread.php?t=2173870
or
http://forum.xda-developers.com/showthread.php?t=2358738
BTW, if they unlocked the device for a different carrier, going back to stock will revert you the the original carrier before.
Click to expand...
Click to collapse
'''''TAMPERED''''
'''''RELOCKED''''
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.21.3263.04
OpenDSP-v.32.120.274.0909
eMMC-boot
May 3 2013, 17:22:59:1357
So if I want that phone stay unlocked I must flash custom rom?
Mpongr33 said:
'''''TAMPERED''''
'''''RELOCKED''''
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.21.3263.04
OpenDSP-v.32.120.274.0909
eMMC-boot
May 3 2013, 17:22:59:1357
So if I want that phone stay locked I must flash custom rom?
Click to expand...
Click to collapse
Just follow [GUIDE] How to Return to 100% Stock, it has a link to RUU's. Going the RUU route will return you back to stock so you can run the OTA without trouble.
majmoz said:
Just follow [GUIDE] How to Return to 100% Stock, it has a link to RUU's. Going the RUU route will return you back to stock so you can run the OTA without trouble.
Click to expand...
Click to collapse
But if I flash stock, phone will bi locked to original carrier? I want to flash over this thread http://forum.xda-developers.com/showthread.php?t=2265618 but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...
Mpongr33 said:
But if I flash stock, phone will bi locked to original carrier? I want to flash over this thread http://forum.xda-developers.com/showthread.php?t=2265618 but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...
Click to expand...
Click to collapse
If you are set on your new carrier then you need to make sure that your MID is the same as the new carrier. You have SuperCID so you can flash any RUU. If you find your new carrier's RUU when you run it the end results will be stock in your new carrier. There is a tool that you can run to change your bootloader locked or unlock status to what you need it to be. Take a look at this guide (nkk71's SuperGUIDE to returning 100% back to stock) it will provide you with both background information and links. Once you get to stock in the carrier of your choice, update OTA then decide if you want to root, custom recovery and custom roms.
Mpongr33 said:
but in section "Flashing custom recovery" saying Your bootloader needs to be "UNLOCKED". "LOCKED" or "RELOCKED" bootloaders can't flash custom recovery and mine phone saying RELOCKED...
Click to expand...
Click to collapse
Recovery:
You need an unlocked bootloader if you want to flash recovery using the ''fastboot flash recovery name_of_recovery.img'' command
like @majmoz said, you can unlock/lock/relock bootloarder using the htc guru bootloader reset tool from custom recovery or via HTCdev.com
now for the RUU part:
because your phone is S-OFF you can flash any ruu (intended for your phone model only: M7_UL). You must make sure both your MID and CID match the ruu you want to use. CID can easily be changed using this command from bootloader:
Code:
fastboot oem writecid YOUR_CID [COLOR="Red"]<----- 8 characters exactly, in most cases, 2 underscores i.e HTC__001[/COLOR]
then you can change your MID (if required) using this tool from custom recovery.

[Q&A] [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmwar

[Q&A] [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmwar
Q&A for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
s_off question
liam_davenport said:
I had no problem with receiving update with the stock recovery installed
---------- Post added at 10:49 AM ---------- Previous post was at 10:47 AM ----------
Don't go from 4.x.xxx.xx to 5.xx.xxx.xx I've had the firmware bug that bricks you're device, it's a pain have to set up linux and run some commands
Click to expand...
Click to collapse
will the process retain s off? Thanks in advance
crazyandroid said:
will the process retain s off? Thanks in advance
Click to expand...
Click to collapse
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
alray said:
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
Click to expand...
Click to collapse
Thank you for the quick reply.
running into a problem
First time back with an HTC since the nexus one. so bear with my on the of the HTC exclusive setting, options and what not.
I keep getting an error code "FAILED (remote: 99 unknown fail)" when i try and flash the ROM, I get the error code in the same spot i would get an error the first time I ran the code. this is a different code than what he said I would get. any direction on what i need to change is greatly appreciated!
Here is the code i get --------------------------------
Tanners-MacBook-Pro:Mac Tanner$ ./fastboot flash zip RUU-HTC_One_GE-4.4.2-3.62.1700.1_Rooted.zip
sending 'zip' (514596 KB)...
OKAY [ 20.864s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 21.109s
Tanners-MacBook-Pro:Mac Tanner$
--------------------------------------------------------------
sOther Information:
Build Number 4.18.502.7 CL302626
Baseband Version "Unknown"
HBOOT 1.44
Radio 4A.17.3250.20
That might be a corrupted download. Did you try redownloading it?
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
teport said:
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
Click to expand...
Click to collapse
you indeed need s-off to flash this ruu and you'll (maybe) have to change your cid/mid to match the android-info.txt file packed in that ruu.
Achieving s-off on hboot 1.44 is simple:
flash ARHD 31.6 (this rom is pre-rooted and have the correct unsecured kernel for the s-off exploit to work)
Then follow instructions from Revone thread.
when s-off is acheived, confirm that your cid and mid match the android-info.txt file of the ruu (or change CID/MID so they match)
Flash the ruu in RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip
fastboot reboot
Never s-on and relock bootloader when using GPE
Can I just flash the newest firmware? Or there is a different firmware for gpe?
htc one m7 convert GPE questions.
htc one m7
model pn07100
android 4.3
htc sense 5.0
hboot 1.55
unlocked
I want to convert my m7 to a GPE. before i do anything to my phone ,I have a few questions to ask...
i want to install the RUU-HTC_One_GE-4.4-3.62.1700.1.zip rom (non rooted) http://forum.xda-developers.com/showthread.php?t=2358781
- does that mean i dont need to root my phone if im flashing the non rooted rom?
- my device is unlocked but in the bootloader is says that its locked in the menu. does that mean i still have to unlock the bootloader? is there a difference between having an unlocked phone and having an unlocked bootloader?
- do i need to install sync manager and install drivers for my phone?
- will i be able to receive updates from google OTA? do i need to flash stock recovery in order to receive OTA updates from google?
- how would i back up my stock rom (android 4.1.2 w/ htc sense 5.0) if i decide to go back.
- after the flash will i have to re-install all my apps?
thanks.
S-off mandatory
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
duzera said:
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
Click to expand...
Click to collapse
are you asking seriously or....?
Prerequisites
S-Off, <--------
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1
i installed the google play edition for htc one m7 4.4.2 rom. how do i add/remove panels? i dont see any personalize settings in the menu? i've tried a search and no results.
graphic glitches
I have successfully converted my phone to GPE4.4.2 using the exact methods. There is no problem with that. Problem started once I did an OTA to update it with 4.4.3 where there are graphic glitches on the status bar and the bottom part of the screen. Also the power off panel won't appear after pressing (holding) the power button. Anyone suffered this? any solutions?
Edited : Problem solved by changing phone's CID. I can't change the RUU android-info's CID because the glitch would be there as the OTA's CID is GOOGL001.
Sprint?
Hey guys, does this RUU work with Sprint yet?
when upgrade to lollipop
have this problem: mount failed to mount /dev/block/mmcblk0p037 at /data device or resource busy
how to solve it ?
in 4.4.4, stuck recovery, unrooted
It doesn't affect anything. Just let it keep going. The update takes a while because it is using the older patch method.
recovery
where can I find stock recovery for gpe rom 4.4.4/4.9.1700.1 thanks in advance
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Cillian.K said:
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Click to expand...
Click to collapse
wrong cid make sure your cid is compatible with the ruu

Categories

Resources