Database Develop

[Q] Struggling to Unroot Device

I wonder if anybody is able to assist at all?
I have a root HTC One M7 which I am having a lot of trouble returning to stock recovery. I am not using a custom ROM.
I've read multiple different forums and threads/techniques none of which I've been able to use successfully. Any help would be greatly appreciated.
The device is running Android v4.3 and when I went to identify the CID = GOOGL001
Which files should I be using to reflash the recovery?
Should the bootloader already be relocked?
I've seen all sorts of variance in advice but nothing which seems to work, and right now I have a device that will not boot properly, likely as the boot.img one of the techniques suggested was no good.
Thanks in advance. :cyclops:

Was it unlocked when you bought the device, if so, flash any unlocked ruu, this needs to be done using fastboot
Sent from my HTC One using XDA Premium 4 mobile app

speedyjay said:
Was it unlocked when you bought the device, if so, flash any unlocked ruu, this needs to be done using fastboot
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No it was locked.

Anybody else have any ideas?
the device is S-on and I cant change that as I can't boot the device through to the OS. Massive problems.

Has anybody discovered anything further on these devices with S-on? I managed to flash a Google Play edition firmware to the device which has it working and not rooted. However, it is not the correct firmware for the device and now I cannot update the device to new OS or some other things also like issues with WiFi etc..
Any help gratefully received. :fingers-crossed:

coligulus said:
Has anybody discovered anything further on these devices with S-on?
Click to expand...
Click to collapse
What do you mean here? What is your issue with the device and what is your goal?

alray said:
What do you mean here? What is your issue with the device and what is your goal?
Click to expand...
Click to collapse
Hi Alray, thanks for your response.
I have an HTC One M7 device which was rooted to conduct some research. I am trying to return the device to stock, not as I need a repair, just as I need a stock ROM back on the device. Due to the device being set to S-On I understood that there were some issues doing this. Subsequently when attempting to unroot I had a number of problems. The device was bricked for a long time. I finally found a Google Play version ROM for the HTC One which worked, however I have not been able to flash the stock recovery and thus I can now no longer use the OTA update function on the device.
Does that explain well enough or is there anything I can share to help with an answer. Thank you for taking the time to write.

coligulus said:
Hi Alray, thanks for your response.
I have an HTC One M7 device which was rooted to conduct some research. I am trying to return the device to stock, not as I need a repair, just as I need a stock ROM back on the device. Due to the device being set to S-On I understood that there were some issues doing this. Subsequently when attempting to unroot I had a number of problems. The device was bricked for a long time. I finally found a Google Play version ROM for the HTC One which worked, however I have not been able to flash the stock recovery and thus I can now no longer use the OTA update function on the device.
Does that explain well enough or is there anything I can share to help with an answer. Thank you for taking the time to write.
Click to expand...
Click to collapse
So yoou only need to flash the stock recovery for your phone?
please post the output of
Code:
fastboot getvar all
minus IMEI/SN

alray said:
So yoou only need to flash the stock recovery for your phone?
please post the output of
Code:
fastboot getvar all
minus IMEI/SN
Click to expand...
Click to collapse
Apologies for the delayed response.
ERROR: could not get pipe properties
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: ********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3858mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

coligulus said:
Apologies for the delayed response.
ERROR: could not get pipe properties
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: ********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3858mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
are you prompted there is an ota available.? If yes download it and extract the recovery.img file from the ota and then flash it to your phone.
Have you tried to restore your phone with this ruu.zip here?

alray said:
are you prompted there is an ota available.? If yes download it and extract the recovery.img file from the ota and then flash it to your phone.
Have you tried to restore your phone with this ruu.zip here?
Click to expand...
Click to collapse
Thanks for your response. I am prompted to update with an OTA KitKat update, however when selecting to update the device reboots to apply update but comes to Fastboot only and goes no further. How should I go about applying this update if not like that?
I am just downloading the RUU you linked to to see if that helps..
Thanks again.

coligulus said:
Thanks for your response. I am prompted to update with an OTA KitKat update, however when selecting to update the device reboots to apply update but comes to Fastboot only and goes no further. How should I go about applying this update if not like that?
I am just downloading the RUU you linked to to see if that helps..
Thanks again.
Click to expand...
Click to collapse
The response received when attempting to flash that RUU was as follows:
Downloads $ fastboot flash zip RUU\ Zip\ M7_Google\ Edition_4.4_3.58.1700.5.zip
ERROR: could not get pipe properties
target reported max download size of 1526722560 bytes
sending 'zip' (506183 KB)...
OKAY [ 17.258s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 70.149s
Any other ideas?

[Q] Back to Stock for Bell HTC One

I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.

Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s

Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)

kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.

Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now

I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.

Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?

Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.

Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse

As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.

SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.

Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.

SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.

Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!

Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched

ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.

Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process

[Q] Stuck in boot loop after HTC1GURU reset

I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.

Sklirg said:
I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Click to expand...
Click to collapse
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Could you post your fastboot getvar all please without the imei and serial numbers please.

Seanie280672 said:
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Click to expand...
Click to collapse
That makes sense.
Seanie280672 said:
Could you post your fastboot getvar all please without the imei and serial numbers please.
Click to expand...
Click to collapse
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
Thanks

Sklirg said:
That makes sense.
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
Thanks
Click to expand...
Click to collapse
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip

Seanie280672 said:
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
Click to expand...
Click to collapse
Thank you! This worked wonders.

Sklirg said:
Thank you! This worked wonders.
Click to expand...
Click to collapse
Your welcome, that's what we're here for :good:

[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)