Database Develop

[Q] m7_u HBOOT MOD help? [SOLVED]

Hi, I've been trying to remove the red text from splash screen (I changed the splash to include owner info) for my phone but so far no luck. I've been spending the night searching the forums and it seems that changing the HBOOT would solve my problem. However I can't seem to find one compatible for my phone. Is there any other way for me to do so?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.709.103
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ******************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would appreciate any help from anyone who can point me to the right direction. (BTW, OTA is 5.12.709.103)
Thanks in advance

I flashed my s-off GSM phone with a full Google Play Edition RUU which contains a really nice black bootloader with a little gray padlock. If you don't want to do that there is a dev thread for installing a custom hboot that you can use to remove the red text. If you cant find it let me know and I'll see if I can find it.

xtalks said:
Hi, I've been trying to remove the red text from splash screen (I changed the splash to include owner info) for my phone but so far no luck. I've been spending the night searching the forums and it seems that changing the HBOOT would solve my problem. However I can't seem to find one compatible for my phone. Is there any other way for me to do so?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.709.103
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ******************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would appreciate any help from anyone who can point me to the right direction. (BTW, OTA is 5.12.709.103)
Thanks in advance
Click to expand...
Click to collapse
you can flash any modified m7_u firmware which will contain a modified HBOOT to remove red text, due to being s-off, you must change your cid and mid to match the firmware that you want to use first.
NEVER GO S-ON WITH A MODIFIED HBOOT / FIRMWARE, IT WILL LEAD TO AN INSTANT BRICK.

I do have a lot of questions right now:
dougeedug said:
I flashed my s-off GSM phone with a full Google Play Edition RUU which contains a really nice black bootloader with a little gray padlock. If you don't want to do that there is a dev thread for installing a custom hboot that you can use to remove the red text. If you cant find it let me know and I'll see if I can find it.
Click to expand...
Click to collapse
Is this what you're talking about?http://forum.xda-developers.com/showthread.php?t=2391611
I'd prefer the original white bootloader, if that is not asking too much, and I'm having a hard time looking for custom Hboots for my firmware
Seanie280672 said:
you can flash any modified m7_u firmware which will contain a modified HBOOT to remove red text, due to being s-off, you must change your cid and mid to match the firmware that you want to use first.
NEVER GO S-ON WITH A MODIFIED HBOOT / FIRMWARE, IT WILL LEAD TO AN INSTANT BRICK.
Click to expand...
Click to collapse
Do I need to change the CID/MID of my phone or can I just edit android-info.txt? Would this one work? http://forum.xda-developers.com/showthread.php?t=2485651

xtalks said:
Is this what you're talking about?http://forum.xda-developers.com/showthread.php?t=2391611
I'd prefer the original white bootloader, if that is not asking too much, and I'm having a hard time looking for custom Hboot
Click to expand...
Click to collapse
That is the bootloader I am referring to, although I did not install it separately as it was just "part of the package" when running the GPE RUU. I think thishttp://forum.xda-developers.com/showthread.php?t=2485651 may be more what you are looking for, although I have no idea if the specific hboot offered is the one you need.

dougeedug said:
That is the bootloader I am referring to, although I did not install it separately as it was just "part of the package" when running the GPE RUU. I think thishttp://forum.xda-developers.com/showthread.php?t=2485651 may be more what you are looking for, although I have no idea if the specific hboot offered is the one you need.
Click to expand...
Click to collapse
I am actually contemplating on flashing that specific HBOOT right now (check my reply to Sean), but I wouldn't know what to do if it does brick my phone. >_<

It can be a significant risk considering that the bootloader is basically the lowest tier of connectivity users like us have, therefore offering little in the way of options for recovering from a failed attempt.. I suggest reading that whole thread and seeing what has been happening to others. I assume that any attempt to flash a new hboot would fail harmlessly if something did go wrong. The main thing to consider is that no matter what we do to our s-off HTC devices, we have the luxury of bringing the device home to mama with a full RUU flash. If a failed hboot install blocks you from accessing the RUU mode, then you may be well and truly screwed. But all that being said, I have installed a custom hboot once before (I cant even remember why now, perhaps it was pre GPE) and everything went just fine. It goes without saying that you should read the OPs directions over and over until you are sure you have your head all the way around what you are doing before you begin. Also, as the user above offered in quite justified allcaps, you must NEVER EVER try to go back S-on while running a nonstock hboot! This will result in a device recoverable only by jtag service.

Thanks all. Followed this guide (http://forum.xda-developers.com/showthread.php?t=2365506) with my fingers crossed and all was well.

xtalks said:
Thanks all. Followed this guide (http://forum.xda-developers.com/showthread.php?t=2365506) with my fingers crossed and all was well.
Click to expand...
Click to collapse
Edit your thread title with a [SOLVED] tag and I will pay you for it by hitting your thanks button!

[Q] How do I go from Viper Rom back back to stock to sell phone?

I have a HTC one with Viper Rom I want to go back to 100% stock to sell. I started this process days ago and I think my first step was to lock the bootloader then try to find an RUU to run. That look about 3 days off my life with bootloops until I locked the bootloader again and now have my phone back.
Here are my specs I think the experts will need- can the helpful community here help me get back to stock and direct me what steps to use?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146603692
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

cfclay said:
I have a HTC one with Viper Rom I want to go back to 100% stock to sell. I started this process days ago and I think my first step was to lock the bootloader then try to find an RUU to run. That look about 3 days off my life with bootloops until I locked the bootloader again and now have my phone back.
Here are my specs I think the experts will need- can the helpful community here help me get back to stock and direct me what steps to use?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34JS902192
(bootloader) imei: 990001466036928
(bootloader) meid: 99000146603692
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Try this RUU
https://www.androidfilehost.com/?fid=23329332407573774

Thanks, I'm pretty sure I already tried that, but maybe I did the wrong steps or wrong order.
Do I just run that RUU ....no relock or anything else first?
Sent from my HTCONE using XDA Free mobile app

cfclay said:
Thanks, I'm pretty sure I already tried that, but maybe I did the wrong steps or wrong order.
Do I just run that RUU ....no relock or anything else first?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
You can find the instructions for running the RUU here. But here is a more current RUU which I think will match your hboot 1.57. Follow the instructions in the OP.

Thanks, as I recall I tried exactly those steps and that is how I ended up in a boot loop.
Specifically when I ran the RUU it would complete maybe steps 1 of 5 and I would get an error and the program would stop with error 'htc fastboot.exe has stopped working "
Pretty much no method I tried worked until I relocked the boot loader and voila the phone booted finally.
Notice I have higher boot loop version. Does that matter?
Sent from my HTCONE using XDA Free mobile app

cfclay said:
Thanks, as I recall I tried exactly those steps and that is how I ended up in a boot loop.
Specifically when I ran the RUU it would complete maybe steps 1 of 5 and I would get an error and the program would stop with error 'htc fastboot.exe has stopped working "
Pretty much no method I tried worked until I relocked the boot loader and voila the phone booted finally.
Notice I have higher boot loop version. Does that matter?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Please remove from your first post your imei and serialno.
You have a higher hboot, and I think you tried to run a RUU of a lower hboot. Since, you are S-ON you can only run RUU with the same or higher hboot, the same or higher OS/version and the CID & MID must match. If these are not met, it will fail. And the bootloader must be LOCKED or RELOCKED.

majmoz said:
Please remove from your first post your imei and serialno.
You have a higher hboot, and I think you tried to run a RUU of a lower hboot. Since, you are S-ON you can only run RUU with the same or higher hboot, the same or higher OS/version and the CID & MID must match. If these are not met, it will fail. And the bootloader must be LOCKED or RELOCKED.
Click to expand...
Click to collapse
THANK YOU! Another customer serviced. Every issue I encountered I tried to search the answer, and I never found that RUU I guess. You are lifesaver!

Need T-Mobile KitKat rom

I need a T-Mobile or international stock rom sense 5.5 KitKat to to flash on my M7. I now have the AT&T unlocked and rooted but I want to make it a fully functional tmobile device with ota updates and mms and stuff (cause as of now mms don't work, but everything else does. It's a well known issue)
So of you could point me in the direction of a stock sense 5.5 KitKat rom I'd be very great full.
PS: I don't want lollipop. I don't like it. Personal preference.

test_subject said:
I need a T-Mobile or international stock rom sense 5.5 KitKat to to flash on my M7. I now have the AT&T unlocked and rooted but I want to make it a fully functional tmobile device with ota updates
Click to expand...
Click to collapse
So you will first need s-off to flash a t-mobile RUU.
(cause as of now mms don't work, but everything else does. It's a well known issue)
Click to expand...
Click to collapse
Is your APN correctly set? Most of the time, MMS issues are only caused by bad APN. Also caused by add blocking apps like AdblockPlus.
So of you could point me in the direction of a stock sense 5.5 KitKat rom I'd be very great full.
Click to expand...
Click to collapse
Post the output of ''fastboot getvar all', don't post your imei / serialno.
Btw may I ask you why do you want to have ota update support if you want to stay on Kitkat?

alray said:
So you will first need s-off to flash a t-mobile RUU.
Is your APN correctly set? Most of the time, MMS issues are only caused by bad APN. Also caused by add blocking apps like AdblockPlus.
Post the output of ''fastboot getvar all', don't post your imei / serialno.
Btw may I ask you why do you want to have ota update support if you want to stay on Kitkat?
Click to expand...
Click to collapse
Ok. Thank you. I have tried as many apn configurations as i could find to fix the mms/group text but nothing works. I dont have ad block either. Here's the output of "fastboot getvar all":
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Angel>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid:
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\Users\Angel>
and as for the why of wanting otas but wanting to stay on kitkat, I guess it is just for my own sanity, knowing that the rom I have has the capability of recieving an ota is something I'd prefer, but I guess I could settle for a stock rom on the latest kitkat.
Thanks for your help (and sorry i took so long to reply)

test_subject said:
C:\Users\Angel>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: ??
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Yep, you'll need s-off if you want to flash a t-mob ruu because you will need to change your AT&T CID to T-Mobile and your MID to PN0710000. Btw why the MID (modelid) line is blank? It should currently be PN0712000...

alray said:
Yep, you'll need s-off if you want to flash a t-mob ruu because you will need to change your AT&T CID to T-Mobile and your MID to PN0710000. Btw why the MID (modelid) line is blank? It should currently be PN0712000...
Click to expand...
Click to collapse
Ok thanks. It's blank because I thought that was one of the things you told me not to post, sorry. So after getting s-off and flashing the t-mobile ruu, will I still be rooted? Also, where might I find a t-mobile ruu for KitKat? Or a similarly stock rom, because I just mainly want to get rid of the AT&T
Thank you

test_subject said:
Ok thanks. It's blank because I thought that was one of the things you told me not to post, sorry. So after getting s-off and flashing the t-mobile ruu, will I still be rooted? Also, where might I find a t-mobile ruu for KitKat? Or a similarly stock rom, because I just mainly want to get rid of the AT&T
Thank you
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
After flashing a ruu, you will not have root anymore, you'll have to re-flash a custom recovery and supersu binaries.

M7 Trying to get back to stock-but need a helping hand

hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(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: 4197mV
(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
thanks in advance

bacon165 said:
hey guys, i am now about to sell my m7 after over 2 years
a long time ago when i unlocked the boot loader, and installed tmrp i made a backup of my stock ROM. its been on a usb pen along time now. so today i used twrp to restore it. all when well i then decided to relock the bootloader using fastboot. in my ignorance i thought this was all i would need to do. upon reboot a rom update was found 6.09.401.10. i am currently 6.09.401.5. downloaded and restarted to install the update. recovery wouldnt load. okay that from the twrp flash replacing it. so of course onto xda to find a stock recovery. i believe i found it. but now i am worried- do i need to re unlock the bootloader? will i need to get the token again? or do i need the rru.exe 6.09.401.10? what is the best way to do this as unsure what to do next? as it will need ota updates. i have added my version info below just encase its needed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37WW905236
(bootloader) imei:
(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: 4197mV
(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
thanks in advance
Click to expand...
Click to collapse
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).

This is the link to the RUU. Install the file on PC (it is a big file) and connect your phone and run it.
Should return you to stock Lollipop 5.0.2 with Sense 6.
Download the right one for your variant:
htc.com/us/support/htc-one/news/ (Unlocked/Developer Edition)
htc.com/us/support/htc-one-t-mobile/news/
htc.com/us/support/htc-one-sprint/news/
htc.com/us/support/htc-one-verizon/news/
htc.com/us/support/htc-one-att/news/

alray said:
To flash a recovery, even if its the stock one, the bootloader must be unlocked. Unfortunately, unlocking the bootloader requires the stock recovery....
I would keep the bootloader locked and flash the latest RUU version for this phone (7.19.401.51). Look in the general section (in the sticky threads) there is one named "Lollipop RUU collection". You'll find that RUU at post #2 and instructions how to flash at post #1. Be sure to use the fastboot version (htc_fastboot) instructed at post #1 (you can't flash a 7.xx.xxx.x ruu with the fastboot version from the android sdk tools).
Click to expand...
Click to collapse
Thank you alray for your fast reply i am currently downloading 7.19.401.51 (signed version)
is it the downgrade instructions i need to follow?

Thank you for your reply
my version is the European (uk version)
i am currently downloading the 7.19.401.51 from xda, might take about 2 hours, i will keep you informed with my progress
thanks

bacon165 said:
is it the downgrade instructions i need to follow?
Click to expand...
Click to collapse
No, going from 6.xx.xxx.x to 7.xx.xxx.x isn't a downgrade.
Sent from my HTC One using XDA Labs

Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise

bacon165 said:
Hey Alray
I followed the instructions and the advised you gave me
my HTC M7 is now back up and running RUU installed no problem
thank you again for your guidance/advise
Click to expand...
Click to collapse
You're welcome
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)