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
Related
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.
Hi guys, when i've try to install official ruu 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.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Antoo1984 said:
Hi guys, when i've try to install official ruu 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.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Click to expand...
Click to collapse
which HBOOT version are you on ?
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
raghav kapur said:
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
Click to expand...
Click to collapse
i'm on hboot 1.56
Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Not really, With S-ON you can flash signed ruu of same or higher version with bootloader LOCKED or RE-LOCKED.
S-OFF is only needed to flash unsigned RUU or for downgrading, and with S-OFF you can flash a RUU with a locked/relocked or unlocked bootloader.
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
Edit: So you were on 4.19.401.11 before flashing 4.19.401.9 ? You can't downgrade with S-ON
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru 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
and i've got the error
now what can i do?
Antoo1984 said:
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru 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
and i've got the error
now what can i do?
Click to expand...
Click to collapse
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
raghav kapur said:
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
Click to expand...
Click to collapse
i've try to unlock bootloader but noting happen, say always relocked
Antoo1984 said:
i've try to unlock bootloader but noting happen, say always relocked
Click to expand...
Click to collapse
You don't get to the unlock bootloader option ??
no nothing
Antoo1984 said:
no nothing
Click to expand...
Click to collapse
I really don't know if there is a solution, maybe we could ask @nkk71 if he have an idea....
OP is stuck in ruu mode after an incomplete ruu flash from 4.19.401.11 to 4.19.401.9. S-ON, bootloader relocked (not able to unlock again). THe only option in bootloader is RUU in orange.
Antoo1984 said:
no nothing
Click to expand...
Click to collapse
Yes, @nkk71 might have an idea. Im just sharing what I know- If you cannot get into fastboot also, you really have a serious problem. Your only option (not 100% sure) is an RUU based on 4.19.401.11, which doesn't currently exist. If there is another solution, I don't know. But I think you will have to wait for an RUU based on your version.
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
That screenshot does not look nice!
you're firmware is in limbo... from the looks of it, you did the first flash, but didn't do the second flash.
So first make sure the RUU you have is not corrupt, the MD5 should be 9AD4111CE86981E3DFFCCE6D9EE80551
Second, do you still have a custom recovery installed, or a rooted ROM?
I've stock recovery , i'm sure
Before i've a stock rom by grureset
I can use ruu 4.19.401.9? Or can i flash rom.zip with fastboot?
Inviato dal mio GT-N8000 usando XDA Premium HD app
Finally i've found a solution!!!!
i've downloaded the ota 4.19.401.11 extract firmware.zip
flash it with fastboot 2 times and now i can access to bootloader!!
Thanks for support
Hello everyone,
I was trying diiferent Roms and kernels for many days, but no luck with s-off and sim unlock till today (5 days passed). I hope my gide will help you with your phone as well.
I have Sprint HTC One M7 HBOOT 1.57, OS 5.03.651.3.
1) Unlock bootloader
2) Flash "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
3) Install Super user
4) Flash "m7wls_Stock_Rooted_5.03.651.3_DeOdex_Full" Rom using recovery
5) Flash kernel "ElementalX-sprint-m7-13.1"
6) Use "Firewater", instraction 1 worked for me link: http://firewater-soff.com/instructions/. Now you must be S-Off
7) Downgared to Hboot 1.44. This one worked for me "hboot_hexed"
8) Install Sprint_HTC_One_m7wls_1.29.651.10_RUU
9) Flash againe "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
10) Install Super user
11) Follow all steps in this thread http://forum.xda-developers.com/showthread.php?t=2386703 and you are done.
Thank you.
thanks for sharing the steps, i just got s-off tonight on hboot 1.57 by htc dev unlocking, flashinging twrp recovery which installed super su root. Firewater didn't work at that point, so i flashed CM11 nightly and then firewater s-off worked when "opening bottle 1".
I then installed the firewater hboot, but i'm not sure why is there an advantage to downgrading to an older hboot version? is it just so you can potentially install older RUUs?
it's work for me ) ) thanks your solultion ! very good
so now my HTC one camera not work ) maybe because downgare softwave ... everyone help me ! thanks
dmik said:
Hello everyone,
I was trying diiferent Roms and kernels for many days, but no luck with s-off and sim unlock till today (5 days passed). I hope my gide will help you with your phone as well.
I have Sprint HTC One M7 HBOOT 1.57, OS 5.03.651.3.
1) Unlock bootloader
2) Flash "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
3) Install Super user
4) Flash "m7wls_Stock_Rooted_5.03.651.3_DeOdex_Full" Rom using recovery
5) Flash kernel "ElementalX-sprint-m7-13.1"
6) Use "Firewater", instraction 1 worked for me link: http://firewater-soff.com/instructions/. Now you must be S-Off
7) Downgared to Hboot 1.44. This one worked for me "hboot_hexed"
8) Install Sprint_HTC_One_m7wls_1.29.651.10_RUU
9) Flash againe "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
10) Install Super user
11) Follow all steps in this thread http://forum.xda-developers.com/showthread.php?t=2386703 and you are done.
Thank you.
Click to expand...
Click to collapse
Hey, do you have a link to the rom you flashed in step 4? I downloaded this but they said you need s-off to make it happen.
UPDATE: Was able to flash the rom via recovery and flash elementX kernel, the same one you mentioned. After getting to the firewater step I get this error after the first chug:
Kernel contains HTC anti-firewater patch!
Click to expand...
Click to collapse
UPDATE 2: Followed to Step 5, tried firewater and it failed. Tried SIM Unlock and it failed. Replaced HtcOMADM file and tried S-off via firewater and it failed. Tried SIM Unlock and it did everything fine!
Now I just have to find a SIM that works.
Rom link
HTML:
https://www.androidfilehost.com/?fid=23501681358540094
tmuka said:
thanks for sharing the steps, i just got s-off tonight on hboot 1.57 by htc dev unlocking, flashinging twrp recovery which installed super su root. Firewater didn't work at that point, so i flashed CM11 nightly and then firewater s-off worked when "opening bottle 1".
I then installed the firewater hboot, but i'm not sure why is there an advantage to downgrading to an older hboot version? is it just so you can potentially install older RUUs?
Click to expand...
Click to collapse
Downgrade to lower Hboot was needed to sim unlock phone. I could not make it on HBoot 1.57. Thanks
anhphuong8x said:
so now my HTC one camera not work ) maybe because downgare softwave ... everyone help me ! thanks
Click to expand...
Click to collapse
What u wrong with it. Mine works fine.
dmik said:
What u wrong with it. Mine works fine.
Click to expand...
Click to collapse
i don't understand , i update my HTC one so camera work and accept sim ok , but when i call so not listen speaker all speaker in and speaker out ....
---------- Post added at 01:14 PM ---------- Previous post was at 12:41 PM ----------
so now everything ok ^^ i install raido for it thanks so much ...
After Unlocking As You Described
Can I Flash/Update With Latest Version HBOOT 1.57 OS 5.03.651.3?
Will It Remains Unlocked Sim
Or Will Be Locked Again?
Need More Help Plz
anhphuong8x said:
i don't understand , i update my HTC one so camera work and accept sim ok , but when i call so not listen speaker all speaker in and speaker out ....
---------- Post added at 01:14 PM ---------- Previous post was at 12:41 PM ----------
so now everything ok ^^ i install raido for it thanks so much ...
Click to expand...
Click to collapse
Bro I Need Your Help Plz
What Radio You Installed For Speaker/Mike Sound?
Hey please help me i have a HTC One M7 Sprint its bricked
tmuka said:
thanks for sharing the steps, i just got s-off tonight on hboot 1.57 by htc dev unlocking, flashinging twrp recovery which installed super su root. Firewater didn't work at that point, so i flashed CM11 nightly and then firewater s-off worked when "opening bottle 1".
I then installed the firewater hboot, but i'm not sure why is there an advantage to downgrading to an older hboot version? is it just so you can potentially install older RUUs?
Click to expand...
Click to collapse
i need help i cant seem to find the right ruu or guru rest/stock rom for my htc one m7_wls sprint with s-on its bricked i want to restore it i need help i tryed a lot of versions of ruu's none of them work i dont know what to do i am also trying to unlock the carrier from sprint since its both cdma/gsm. if i cant unlock it i just want to restore it back to stock as it was.
this is all i can find out about the phone i dont know which version to download or where to download it Please help if you can.
the hboot is 1.57.000 openDSP -v32.120.274.0909
OS- emmc-boot 2048mb
May 15 2014, 16:31:22.0
Thanks in advance
NYS Android said:
i need help i cant seem to find the right ruu or guru rest/stock rom for my htc one m7_wls sprint with s-on its bricked i want to restore it i need help i tryed a lot of versions of ruu's none of them work i dont know what to do i am also trying to unlock the carrier from sprint since its both cdma/gsm. if i cant unlock it i just want to restore it back to stock as it was.
this is all i can find out about the phone i dont know which version to download or where to download it Please help if you can.
the hboot is 1.57.000 openDSP -v32.120.274.0909
OS- emmc-boot 2048mb
May 15 2014, 16:31:22.0
Thanks in advance
Click to expand...
Click to collapse
Are you s-on or s-off? Check in bootloader.
i need help i cant seem to find the right ruu or guru rest/stock rom for my htc one m
dmik said:
Are you s-on or s-off? Check in bootloader.
Click to expand...
Click to collapse
Its S-On
NYS Android said:
Its S-On
Click to expand...
Click to collapse
If you are unlocked then you need to relocke usind ADB and tiping in it "fastboot oem lock"
Than download ROm Sprint_HTC_One_m7wls_5.03.651.3_RUU from here http://forum.xda-developers.com/showthread.php?t=2795856
If you still want to unlock try my steps from begining.
dmik said:
If you are unlocked then you need to relocke usind ADB and tiping in it "fastboot oem lock"
Than download ROm Sprint_HTC_One_m7wls_5.03.651.3_RUU from here http://forum.xda-developers.com/showthread.php?t=2795856
If you still want to unlock try my steps from begining.
Click to expand...
Click to collapse
Thank you. Your a genius. The phone works now but i still want to unlock the carrier from sprint and use the GSM for other carrier any idea on how to unlock it? Thank you.
NYS Android said:
Thank you. Your a genius. The phone works now but i still want to unlock the carrier from sprint and use the GSM for other carrier any idea on how to unlock it? Thank you.
Click to expand...
Click to collapse
If you still want to unlock try all my steps from begining step by step.
dmik said:
Hello everyone,
I was trying diiferent Roms and kernels for many days, but no luck with s-off and sim unlock till today (5 days passed). I hope my gide will help you with your phone as well.
I have Sprint HTC One M7 HBOOT 1.57, OS 5.03.651.3.
1) Unlock bootloader
2) Flash "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
3) Install Super user
4) Flash "m7wls_Stock_Rooted_5.03.651.3_DeOdex_Full" Rom using recovery
5) Flash kernel "ElementalX-sprint-m7-13.1"
6) Use "Firewater", instraction 1 worked for me link: http://firewater-soff.com/instructions/. Now you must be S-Off
7) Downgared to Hboot 1.44. This one worked for me "hboot_hexed"
8) Install Sprint_HTC_One_m7wls_1.29.651.10_RUU
9) Flash againe "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
10) Install Super user
11) Follow all steps in this thread http://forum.xda-developers.com/showthread.php?t=2386703 and you are done.
Thank you.
Click to expand...
Click to collapse
thanks man this should be sticky this is stupid retarded i went back and forth locking relocking bootload firewater hboot s-off twrp back and forth off badboys rom kept trying ruu 155 error omg googling the heck out of trying to find a hboot to flash stupid stupid hard to find the correct info following now wish me luck picked up this sprint junk and idk even if the imei is good doing all this on a whim
colorsharpkid said:
thanks man this should be sticky this is stupid retarded i went back and forth locking relocking bootload firewater hboot s-off twrp back and forth off badboys rom kept trying ruu 155 error omg googling the heck out of trying to find a hboot to flash stupid stupid hard to find the correct info following now wish me luck picked up this sprint junk and idk even if the imei is good doing all this on a whim
Click to expand...
Click to collapse
155 error fo Ruu because you are not s-off probably.
dmik said:
Hello everyone,
I was trying diiferent Roms and kernels for many days, but no luck with s-off and sim unlock till today (5 days passed). I hope my gide will help you with your phone as well.
I have Sprint HTC One M7 HBOOT 1.57, OS 5.03.651.3.
1) Unlock bootloader
2) Flash "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
3) Install Super user
4) Flash "m7wls_Stock_Rooted_5.03.651.3_DeOdex_Full" Rom using recovery
5) Flash kernel "ElementalX-sprint-m7-13.1"
6) Use "Firewater", instraction 1 worked for me link: http://firewater-soff.com/instructions/. Now you must be S-Off
7) Downgared to Hboot 1.44. This one worked for me "hboot_hexed"
8) Install Sprint_HTC_One_m7wls_1.29.651.10_RUU
9) Flash againe "recovery-clockwork-touch-6.0.4.8-m7spr" or "openrecovery-twrp-2.8.0.2-m7wls.img"
10) Install Super user
11) Follow all steps in this thread http://forum.xda-developers.com/showthread.php?t=2386703 and you are done.
Thank you.
Click to expand...
Click to collapse
I cannot get this to work for me. :\
I get to Android OS, Unlock the lock screen, get a white screen with green HTC letters and then phone reboots.
Hey, I was stupid and missed up my phone. I wanted to update my phone, but because It was rooded I wasn't able to do it. So I decided to begin from start. So I downgraded my Hboot to 1.44 and also stupid to set s-on again. But then I could not install the stock rom 1.29.651.10. So I decided to try a custom rom. So I would be able to set s-off again. But non of them worked. I think that the old Hboot 1.44 is why the roms didn't work. But I can't change my Hboot before my device is s-off.
I'm able to use adb sideload and twrp recovery
Bootloader information
Tampered
Unlocked
M7_WLS PTV SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v32.120.274.0909
eMMC-boot
May 8 2013.16:30:08:-1
Does any one have any suggestions ?
If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.
coal686 said:
If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.
Click to expand...
Click to collapse
I've have already tried rumrunner, but it didn't work for me. I was able to get Viberone 8 to work, but it was very slow. Tried to get s-off but did't work with the Viberone rom. So now i'm trying another one to see if it will allow me to get the phone s-off. But thx for your respond
1.29.401.12. is not a Sprint rom.
BD619 said:
1.29.401.12. is not a Sprint rom.
Click to expand...
Click to collapse
Sorry ment 1.29.651.10
christian8220 said:
Sorry ment 1.29.651.10
Click to expand...
Click to collapse
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.
BD619 said:
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.
Click to expand...
Click to collapse
Here you go
christian8220 said:
Here you go
Click to expand...
Click to collapse
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again
BD619 said:
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again
Click to expand...
Click to collapse
Thx it worked for me. First I replaced the TWRP recovery with the stock recovery 1.29.651.10. After that I relocked my bootloader "fastboot oem lock" and the device rebooted. I used the 1.29.651.10 RUU exe. and it worked. So thank you, have a nice day
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
reealumni said:
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
Click to expand...
Click to collapse
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
alray said:
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
Click to expand...
Click to collapse
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
reealumni said:
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
Click to expand...
Click to collapse
At first you need a running system cause sunshine is an app based service. After that you can download the latest sunshine app and install it, then the app will test your device if it is possible to make it s-off. If it can, in the second step you have to buy a license for your device within sunshine (about 20€/25$). After sucessfully payment your device will reboot and sunshine will set it to s-off.(The license is bind to your device and you can use it on this device as often as you want, for other devices you need to buy another license)
http://theroot.ninja/
phone is now working but...
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
If after flashing the RUU your problem isn't fixed, it's probably an hardware problem.
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
KARIM9377 said:
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
Click to expand...
Click to collapse
will try reflash the RUU. i do not have any backups of the partitions :crying: