Related
hello. i've just having 4.2.2 ota. i have unlocked bootloader . but revone doesn't work to s-off, allways "segmentation fault (core dumped) when using command " ./revone -P". how to do to re "locked" without revone ??
Fastboot oem lock
gunnyman said:
Fastboot oem lock
Click to expand...
Click to collapse
it's for re s-on that ,i am allready in s-on , i want to "locked" hboot...arggg no flash ,no Tools ....!!! :-s
i have try my usual RUU and it's not compatible with the 4.2.2 ...i wanted to downgrade and use revone to re "locked" (./revone -l -t )... and re- ota with 4.2.2 cleanly but....
absynte said:
it's for re s-on that ,i am allready in s-on , i want to "locked" hboot...arggg no flash ,no Tools ....!!! :-s
i have try my usual RUU and it's not compatible with the 4.2.2 ...i wanted to downgrade and use revone to re "locked" (./revone -l -t )... and re- ota with 4.2.2 cleanly but....
Click to expand...
Click to collapse
You can't s-off if you took the 4.2.2 ota. Revone doesn't work on that hboot.
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.
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
i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?
For_itembine said:
i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?
Click to expand...
Click to collapse
To get your bootloader back to LOCKED, first you need to unlock the bootloader and flash CWM. then flash this zip in CWM:
http://www.htc1guru.com/guides/guru-bootloader-reset/
Choose the option so set the bootloader back to LOCKED. You can also remove TAMPERED using this tool
To go back to S-ON, after setting the bootloader back to LOCKED, enter fastboot mode and type this in Command Prompt without the inverted comma,
"fastboot oem writesecureflag 3"
then follow the on-screen instructions to S-ON. reboot 3 times after the procedure
Feel free to ask any doubts and hit the THANKS button if I helped you
S-on on 1.55/56 hboot may bring back tampered text in bootloader. You have to be on 1.44 hboot to do it. Why do you need to s-on. Its not recommended
sent from my mobile device
raghav kapur said:
To get your bootloader back to LOCKED, first you need to unlock the bootloader and flash CWM. then flash this zip in CWM:
http://www.htc1guru.com/guides/guru-bootloader-reset/
Choose the option so set the bootloader back to LOCKED. You can also remove TAMPERED using this tool
To go back to S-ON, after setting the bootloader back to LOCKED, enter fastboot mode and type this in Command Prompt without the inverted comma,
"fastboot oem writesecureflag 3"
then follow the on-screen instructions to S-ON. reboot 3 times after the procedure
Feel free to ask any doubts and hit the THANKS button if I helped you
Click to expand...
Click to collapse
given link expired...
Please provide the alternate
Thank you
For_itembine said:
i know revone doesnt work to S-oFF, but can i revert back to S-on and remove "RELOCKED" on hboot 1.56 KITKAT 4.4.2?
or is the only way running a RUU, (then running revone) than updating to KITKAT with S-ON and ***RELOCKED*** removed?
Click to expand...
Click to collapse
Yes, revone -l will set back to LOCKED state on any hboot version. Or simply this command in a terminal or adb shell will do it:
Code:
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
Do not go back S-ON, just don't.
Here you go buddy:
http://forum.xda-developers.com/showthread.php?t=2541082
Read all instructions before beginning. Make sure you have the original ADB drivers and the HTC provided drivers coming from HTC sync. Make sure HTC sync is then uninstalled. Make sure your firewall and antivirus is disabled through the process. Make sure you follow all directions to a T. Done this twice following this guide.
Hi everyone. I searched for around half an hour through google and failed to find a situation identical to mine (maybe i havent looked long enough).
I was one step away from resetting the warranty by removing root and locking bootloader again so that i could send it to HTC for repair (its under warranty.
I locked the bootloader and turned s-on. Then after flashing a stock ruu (i was sure i had the correct version) it returned to bootloader and all of a sudden it says TAMPERED again with s-on..
The phone now will not get out of bootloader. Since its s-on i cant flash a rom or recovery or flash a ruu. When trying to flash a stock ruu it says signature verify fail
ran fastboot getvar all
Phone details:
Bootloader: 1.44.0000
Baseband 4V.13.3231.27
Currently TAMPERED bootloader, LOCKED with S-ON.
How do i now get s-off again from this position?
Thanks in advance!
UPDATE:::: I unlocked bootloader through HTCDEV. THis can be closed
You should be able to get S-off again using Revone with HBOOT 1.44. You should be able to find everything you need here http://forum.xda-developers.com/showthread.php?t=2314582 . I was unable to flash any RUU file until I achieved S-off, but I had to use firewater as I couldn't get revone to work with HBOOT 1.57. Here is the firewater link http://forum.xda-developers.com/showthread.php?t=2632351 .