Database Develop

[q] s-off what rom??

Hello XDA-Users,
I have a Question for what I can't find any awnswer...
I have an International HTC One with CID T-MOB101, HBOOT 1.55 and I want to S-OFF.
I already unlocked via HTCDev and flashed a custom Rom.
But with rumrunners S-OFF method it failes every time.. I used many various custom roms, but with no it works.
I can't go back to really stock to try it then, because for this I need S-OFF...
Sometimes it poures 8 times and write then, I have to wait 30 seconds, pray, (...) and try it again. When I tried it again it fails again...
Another time it says you have to flash an other Rom or something else.
So I don't know what Rom to try for getting S-Off..
If someone knows how to fix it, or what Rom to try, write me please.
Please help me
Thanks.

I am having the exact same issue!
My Bootloader Info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3997mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried the rumrunner tool on 4 different PCs, each of them with Windows 7 Ultimate x86 or x64 and always on USB 2.0 port without any Hubs or something like that. The phone was always directly connected to an USB 2.0 port. I also tried different usb cables.
I always ran soju.exe as Administrator and accepted every Superuser request.
ROMs I tried it with: Stock Android 4.3 Sense 5.5, Android Revolution HD 41.0 and ViperOne 3.5.0
I even used an Ubuntu 13.10 Live CD but it never worked.
My bootloader is of course unlocked, TWRP 2.6.3.3 is installed and the phone is/was rooted on every rom I tried.
I attached the linux terminal log and the windows cmd log.
EDIT: I used the latest rumrunner v0.5.0.

Yep
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...

judufu said:
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...
Click to expand...
Click to collapse
try flashing this 4.3 sense 5.0 rom
http://www.scottsroms.com/downloads.php?do=file&id=466
and here's an even older one 4.1.2 you may try
http://www.scottsroms.com/downloads.php?do=file&id=442

Does it work for you?

judufu said:
Does it work for you?
Click to expand...
Click to collapse
I have had s-off since revone was released

Ok, I'll test it at the morning.
Thanks, hope it works

judufu said:
Ok, I'll test it at the morning.
Thanks, hope it works
Click to expand...
Click to collapse
you might want to read this
http://forum.xda-developers.com/showthread.php?t=2487888&page=55

reprekuc malay
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?

TheHellSite said:
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?
Click to expand...
Click to collapse
How do you mean it ??

judufu said:
How do you mean it ??
Click to expand...
Click to collapse
he's referring to this post that was removed
Originally Posted by maspro View Post
Woohoo, I'm a happy person right now.
I made a partition dump of my phone according to this guide: http://forum.xda-developers.com/showthread.php?t=2488772 and provided some additional information about my specific configuration and send it to the Rumrunner devs to see if it was possible to add support for S-OFF. After some emailing back and forth the last couple of days, I agreed to accept the risks and be a test case to see if it was possible to S-OFF my device, since my firmware was to new to make use of the existing exploits Rumrunner 0.5.0 is using. So we had a remote session together..... and a couple of minutes later my phone was S-OFF.
Don't ask me what the devs did, I looked at the adb screen, saw lots of commands and screen output flying around, but for the most part didn't understand it... Anyway my phone is still alive and I'm S-OFF.
Thx devs and I also made a donation (1HE93648R1560915F)!
Click to expand...
Click to collapse

At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.

Great
TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Oh beatiful, when this is like you say...
Wait and hope for the best
Thanks.

TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Am i in the same boat as you? i'm Three (H3G_001) International.
Im getting the same problems as what you described earlier.

Just boot your device into bootloader and then run this command in terminal/cmd "fastboot getvar all".
If the following 3 lines match yours, you very likely are in the same situation.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-main: 3.63.111.3

This it says on my device:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I think some data are nonrelevant for S-Offing, but for completeness.
Hope there are something usefull data for the further process...

(SOLVED) M7 UL won't root, Unable to mount /Data /Cache

Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.

shadowhacker27 said:
Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.
Click to expand...
Click to collapse
Post a screenshot of your bootloader
The RUU's wont install because your S-On and it will only allow same version or higher
the RUU you require is this one...
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
However since your bootloader is unlocked, you could flash a recovery and root from there..
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the recovery in your adb folder and from there
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery and make a backup of your rom.
when you exit TWRP, you will be prompted to root your device

How are you trying to root, and how does it fail? Please provide all the detail you can.

fenstre said:
How are you trying to root, and how does it fail? Please provide all the detail you can.
Click to expand...
Click to collapse
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!

shadowhacker27 said:
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!
Click to expand...
Click to collapse
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings

bored_stupid said:
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings
Click to expand...
Click to collapse
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?

shadowhacker27 said:
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?
Click to expand...
Click to collapse
When you press edit, press on "go advanced.
Sent from my Nexus 7 using XDA Premium 4 mobile app

My HTC one is also driving me mad as I can't install any roms even the original or customs , get always a fault at the end , just boots and is stuck on the boot logo
Sent from my Lumia 1320 using Tapatalk

Active cmdline overflow! Can't enter custom recovery, S-ON

I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.

Frinalal said:
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Click to expand...
Click to collapse
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
http://forum.xda-developers.com/showthread.php?t=2739126

Seanie280672 said:
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
Click to expand...
Click to collapse
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)

Frinalal said:
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Click to expand...
Click to collapse
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
http://forum.xda-developers.com/showpost.php?p=53634257&postcount=90

Seanie280672 said:
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
Click to expand...
Click to collapse
Thanks for helping. I tried it and it still doesn't work. I'll keep searching around the forums to see if I can do anything.

[Q] Relocked bootloader while using custom software, hboot won't detect power button

So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s

adkz25 said:
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
Click to expand...
Click to collapse
Actually they guy there, me, was really busy in the past days and wasn't able to answer everyone. You can't imagine how much PM and Quote I had in the last week And yes I agree with you, its really hard to troubleshoot in that thread since there's so many discussions going on at the same time.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Its a pretty uncommon problem. When flashing a RUU, all partitions (except some partitions that are unique to each devices) are flashed back to stock, even the bootloader which make me believe its not a corrupt bootloader problem. So if after flashing a RUU, your phone still have some problems, its most likely an hardware problem... If the RUU flashed fine there is nothing more you can do on the software side.... THe only thing I can think is to use Sunshine S-OFF to unlock your bootloader but unfortunately it cost 25$ to use Sunshine but at least it will bypass that "power button not working only in bootloader" problem

Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?

adkz25 said:
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
Click to expand...
Click to collapse
I would try the same method they are using in the Verizon HTC One forum, get temp root using kingRoot then launch sunshine
http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099

Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-OFF
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.

adkz25 said:
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
Click to expand...
Click to collapse
Glad it worked!
Firmware files are flashed with fastboot in ruu mode:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip "file name".zip
fastboot flash zip "file name".zip
fastboot reboot-bootloader
Then go in recovery and flash the rom
Better to flash the latest firmware without stock recovery so you don't overwrite twrp recovery with the stock recovery.
Note that this firmware is the latest GPE firmware and that if you want to go back to stock rom using a ruu you'll have to reflash a hboot 1.57 or 1.61 firmware before running a 7.xx.xxx.xx Sense ruu.
GPE roms is perfect if you want something closer to a nexus experience, otherwise stay with a Sense rom.
Sent from my HTC One using XDA Labs

No ROM, No Recovery, Relocked, Tampered, Security Warning

I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=

kayohbe said:
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
Click to expand...
Click to collapse
Please, post the output of "fastboot getvar all" (don't post your imei and serialno).
Sent from my HTC One using XDA Labs

fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s

I recognize this is my own mistake as a result of being short sighted and not careful enough with my actions. Also, i'm willing to take any amount of time necessary to learn whatever skills may be required to resolve this issue (how to utilize certain tools properly, specific programming languages etc.)

kayohbe said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.

alray said:
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
Click to expand...
Click to collapse
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?

kayohbe said:
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
Click to expand...
Click to collapse
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs

alray said:
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?

kayohbe said:
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
Click to expand...
Click to collapse
No its to late, try the RUU.

Seems good [:=
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters

kayohbe said:
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
Click to expand...
Click to collapse
no problem. Update your phone to the latest version before unlocking and rooting. The latest one is .52

One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?

kayohbe said:
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
Click to expand...
Click to collapse
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).

alray said:
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
Click to expand...
Click to collapse
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.

kayohbe said:
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
Click to expand...
Click to collapse
I played the game for 2-3 days at launch and it was easy to spoof a fake gps location to cheat. To do that I also had to hide the fact the I was using "mock location" from the developer options using an Xposed module or the game would detect it. I guess its also really easy to hide the fact the you are using a custom rom/root from pokémon go using the same method... Not tried but im sure it can be done.

I assume it was easy prior to the current update - they've cracked down on 'spoof players' about a week or so ago

Help for HTC - M7
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3952mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction

1191 said:
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3952mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
Click to expand...
Click to collapse
Yes you've download the right file.
Instructions how to flash: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(see post #1)