Develop Bugs

Sunshine

I'm having a problem being able to launch apps on my One M8 ATT... I Don't have any apps on my home page and ATT Ready2Go keeps crashing on me. Can someone give me a command line so I can launch SunShine on my device through ADB, that way I can S-Off and go back to a different ROM.

Why would you need s-off to install a different rom ?

Mr Hofs said:
Why would you need s-off to install a different rom ?
Click to expand...
Click to collapse
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.

isutke1287 said:
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
Click to expand...
Click to collapse
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.

xunholyx said:
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
Click to expand...
Click to collapse
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)

isutke1287 said:
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
Click to expand...
Click to collapse
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.

xunholyx said:
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
Click to expand...
Click to collapse
I can NOT appreciate and thank you for your assistance in this! I went ahead and locked the bootloader and restored the original image with the RUU you linked me to, yesterday. Couldn't wait to try, haha. I had to sweet talk the HTC Live Chat person to tell me if I could use the RUU for the same software version as I had. Phone has been working like a champ. I'm gonna give it another day or two to settle in, do a few backups just in-case the flash doesn't go well.
I will definitely unlock the bootloader again and flash TWRP and SuperSU. But I imagine going S-OFF is just off the table right now since I'm a bit stripped of funds. I can afford it, haha, but my funds are already allocated towards adulting and such.
Again, THANK you for the support! This has been a learning experience.:good::good::good::good::good:

wiped my OS, flashed a poop ROM need help

Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.

What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.

Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).

I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?

I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?

One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?

enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.

I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.

enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.

I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?

I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...

update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.

enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.

I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.

enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.

Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.

Please help me urgently!!!!!

I was following some tutorial and I decided to 'Relock' my bootloader. So I didn't that but then a flag came up underneath it saying "Security Concerns" or something like that. Then using fastboot/ADB I got it to the screen with just the grey HTC text and then I tried to flash the RUU over to the device but I got some error 41 saying the model id check failed. From there I discovered I'm stuck in a bootloop...I can't get into TWRP or boot the phone up at all...Just keeps going back to fastboot. I can't reset or do anything. Please help me get out of this mess and then hopefully help me unroot it!
The CID is: telus001
The version main: 6.13.661.9
The Model ID: OP6B16000
And it is S-ON

Your post is a bit confusing to follow. I'll need some clarification before I can properly help. See my comments below in red font, and try to address them as best you can:
Mavrick1798 said:
I was following some tutorial and I decided to 'Relock' my bootloader. So I didn't that Don't know what that last bit means, I think you left out a word(s). Did you attempt to relock the bootloader or not? If so, was it successful, or did you have errors? Most importantly, on the bootloader screen, does it say the bootloader is LOCKED, UNLOCKED or RELOCKED? My advice is if its unlocked, to leave it that way (more on this later)
Then using fastboot/ADB I got it to the screen with just the grey HTC text and then I tried to flash the RUU over to the device but I got some error 41 saying the model id check failed. I don't your version M8 (Telus) has an RUU. The RUU must match your version carrier ID (CID) and model ID (MID) or it will fail. Normally, I'd ask which version number RUU you tried (there are dozens of different RUUs). But in your case, it doesn't really matter, as I don't think there are any RUUs which will work for you.
From there I discovered I'm stuck in a bootloop...I can't get into TWRP or boot the phone up at all...Just keeps going back to fastboot. I can't reset or do anything. Please help me get out of this mess and then hopefully help me unroot it!
How exactly to proceed depends on whether the bootloader is presently UNLOCKED or not. If its locked, no boot (no OS) is the expected result, as it expects the RUU to be run. My advice would be to unlock the bootloader (if its relocked), flash TWRP, then see if you can then boot into TWRP. From there, restore a stock backup.
Click to expand...
Click to collapse
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number) so we can see more info about the device.

redpoint73 said:
Your post is a bit confusing to follow. I'll need some clarification before I can properly help. See my comments below in red font, and try to address them as best you can:
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number) so we can see more info about the device.
Click to expand...
Click to collapse
C:\Users\Noah\Desktop\RUU>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.661.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Yes sorry about the confusing post, I was running on little sleep. I did succeed in relocking my bootloader and it now reads "***RELOCKED***."
Being that it is relocked could you give me a step by step on how to unlock it and flash TWRP as you mentioned in the ending of your post. Your response gives me hope so thank you so much!

Mavrick1798 said:
Being that it is relocked could you give me a step by step on how to unlock it and flash TWRP as you mentioned in the ending of your post.
Click to expand...
Click to collapse
You can unlock the bootloader again, either by using fastboot command and the unlock bin code you originally used to unlock it. Otherwise, just go through the process again on HTCDev.com, and get a new bin code.
From there, flash TWRP, and then restore the 6.13.661.9 stock TWRP backup using the instructions and files found here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 10, then reboot to OS. No need to restore stock recovery, as there are no more OTA updates for this phone.

Mavrick1798 said:
C:\Users\Noah\Desktop\RUU>fastboot getvar all
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(bootloader) version-main: 6.13.661.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: TELUS001
(bootloader) security: on
Yes sorry about the confusing post, I was running on little sleep. I did succeed in relocking my bootloader and it now reads "***RELOCKED***."
Being that it is relocked could you give me a step by step on how to unlock it and flash TWRP as you mentioned in the ending of your post. Your response gives me hope so thank you so much!
Click to expand...
Click to collapse
redpoint73 said:
Only need to do through Step 10, then reboot to OS. No need to restore stock recovery, as there are no more OTA updates for this phone.
Click to expand...
Click to collapse
just a little heads up ( it's late i know but it might be useful )
here is the correct RUU for your device ( i found it on AFH )
https://www.androidfilehost.com/?fid=24665542585483465
@Mavrick1798
i think you know how to flash it

ahmed.ismael said:
just a little heads up ( it's late i know but it might be useful )
here is the correct RUU for your device ( i found it on AFH )
https://www.androidfilehost.com/?fid=24665542585483465
@Mavrick1798
i think you know how to flash it
Click to expand...
Click to collapse
Can you reupload it?

pjpogi1445 said:
Can you reupload it?
Click to expand...
Click to collapse
actually the file isn't mine and I don't have it
you will have to search for it on the Internet

Only fastboot - no recovery and nothing else

Linux user. Phone won't boot or go into recovery but can be accessed through fastboot. Biggest problem is not able to boot into recovery. My attempts to flash a new recovery .img fail as in https://forum.xda-developers.com/showthread.php?t=2758204.
But I don't know what to put in my android-info.txt to get this solution to work for me. Have S-OFF and RELOCKED boot status.
Any ideas would be great thanks - it is of course driving me mad! (er)
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.512.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 99000499755159
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Solved it: Took 6.12.401.4_NoRedText_TWRP.zip mentioned elsewhere here. Then modified android-info.txt with my modelid and mainver and placed in new zip. Had to flash twice but it worked the second time. Thanks to all those that would have helped!

pir8don said:
Linux user. Phone won't boot or go into recovery but can be accessed through fastboot. Biggest problem is not able to boot into recovery. My attempts to flash a new recovery .img fail as in https://forum.xda-developers.com/showthread.php?t=2758204.
But I don't know what to put in my android-info.txt to get this solution to work for me. Have S-OFF and RELOCKED boot status.
Click to expand...
Click to collapse
You made the solution more complicated/convuluted than necessary; and possibly even dangerous (see more on that below). The reason it says "remote not allowed" when flashing TWRP, is very simple: you can't flash custom recovery with a locked or relocked bootloader, by definition.
The process to unlock bootloader on a Verizon/LRA version M8 with s-off (which yours is) is here: https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 09:13 AM ---------- Previous post was at 09:07 AM ----------
pir8don said:
Solved it: Took 6.12.401.4_NoRedText_TWRP.zip mentioned elsewhere here. Then modified android-info.txt with my modelid and mainver and placed in new zip. Had to flash twice but it worked the second time. Thanks to all those that would have helped!
Click to expand...
Click to collapse
I'm not sure your problems are solved. Once you flash a ROM and get the phone booted, you may (I expect) find the radio is broken (no signal). You can't flash any other (m8 version's) firmware to a Verizon/LRA version M8. You have to be extremely careful what you flash to the Verizon/LRA M8 with s-off. The radio brick is often reversible, but sometimes permanent.
The Verizon version is a bit of an oddball (and the LRA version even more so), in that it is designed to support the US Verizon network, which is a CDMA network. The device also supports GSM and LTE (some bands), but it's that CDMA support that makes the Verizon device (annoyingly) unique.

Yes it is now looking like I don't have radio. Is there a path now to a working radio. I applied https://forum.xda-developers.com/showthread.php?t=2708571 to unlock. Sometimes my ignorance is not bliss!

pir8don said:
Yes it is now looking like I don't have radio. Is there a path now to a working radio. Sometimes my ignorance is not bliss!
Click to expand...
Click to collapse
You can try the RUU meant for your device here: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
If you don't have a microSD card, let me know, and I'll point you to the fastboot install method.
If the RUU doesn't fix the radio problem, it's probably permanently radio bricked. The LRA version doesn't have many RUUs available (the above is the only one I know of) and without other RUUs, you don't have a way to fix the radio.

Thanks heaps RedPoint. It all worked fine and the radio is working too. Your assistance is much appreciated

RUU installation problem

Okay, I think I found the RUU exe file for my device. But I have this problem where it just stuck at Updating... (1/1) Sending...
I'm the RUU file - RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I don't know if I need to be in Unlock/Lock/Relock state of bootloader.
modelid: 0P6B12000
cidnum: CWS__001
Any help would be appreciated.

leelaw said:
Okay, I think I found the RUU exe file for my device. But I have this problem where it just stuck at Updating... (1/1) Sending...
I'm the RUU file - RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I don't know if I need to be in Unlock/Lock/Relock state of bootloader.
modelid: 0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
Correct bootloader state to install RUU would be locked or relocked (unless you have s-off, in which case any bootloader condition will work).
Since the RUU is stuck updating, I believe this usually means that security checks (bootloader locked, MID and CID check, etc.) are already passed. The RUU simply got stuck. If you haven't already done so, it should typically be okay to disconnect the phone, kill the process, etc. and start over again. A lot of times, simply trying the RUU again, will do that trick.
Otherwise, you may need to try another USB port on your PC, another cable, or even another PC. RUU can be quite finicky with the PC setup. It also must be a real PC (not emulated Mac, etc.).
If you also know how, please do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can see the details on your phone. In some circumstances, how you determined the MID and CID may not actually be getting reported correctly (you didn't mention how you determined these, getvar all is the best and most accurate way).

Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s

Jjohnson0830 said:
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. It won't get you help any faster, but will only confuse you and those trying to help you. I posted help in one of the other threads you posted in. Go figure out which one. Now you get it?

redpoint73 said:
Please don't post the same question to multiple threads. It won't get you help any faster, but will only confuse you and those trying to help you. I posted help in one of the other threads you posted in. Go figure out which one. Now you get it?
Click to expand...
Click to collapse
So sorry to have done that.It's won't repeat itself again
Thanks.